linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Jean Delvare <khali@linux-fr.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Eyal Lebedinsky <eyal@eyal.emu.id.au>
Subject: Re: Linux 2.6.16-rc1
Date: Wed, 18 Jan 2006 21:14:01 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.4.61.0601182112190.25325@yvahk01.tjqt.qr> (raw)
In-Reply-To: <20060118191247.62cc52cd.khali@linux-fr.org>

>
>This ain't exactly the same command Sam had me test earlier today. This
>one breaks my /dev/null:
>
>  echo "main() {}" | gcc -xc - -o /dev/null

Right. It gets chmodded 777 here then.
I'd poke on gcc for that, or rather, ld (binutils).


Jan Engelhardt
-- 

  reply	other threads:[~2006-01-18 20:14 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17  8:19 Linux 2.6.16-rc1 Linus Torvalds
2006-01-17 13:16 ` Prakash Punnoor
2006-01-17 13:36   ` Jeff Garzik
2006-01-17 13:49     ` Prakash Punnoor
2006-01-17 16:25 ` Gene Heskett
2006-01-17 18:05   ` Mauro Carvalho Chehab
2006-01-17 20:38     ` Gene Heskett
2006-01-17 17:39 ` Diego Calleja
2006-01-17 18:25   ` Linus Torvalds
2006-01-17 19:06     ` Diego Calleja
2006-01-17 20:08     ` Jan Engelhardt
2006-01-17 21:04       ` Antonio Vargas
2006-01-17 22:05         ` Jan Engelhardt
2006-01-20  8:15           ` L. A. Walsh
2006-01-20  8:28             ` David S. Miller
2006-01-20  8:47             ` Russell King
2006-01-18  0:22     ` Linux 2.6.16-rc1 -- which gcc version? Jeff Chua
2006-01-18  1:14       ` Linus Torvalds
2006-01-18  7:00       ` Arjan van de Ven
2006-01-19 23:42   ` Linux 2.6.16-rc1 Bill Davidsen
2006-01-17 19:27 ` David R
2006-01-18  4:59   ` Greg KH
2006-01-18  9:28     ` David R
2006-01-18 20:57     ` David R
2006-01-18 21:04       ` Greg KH
2006-01-17 19:54 ` Linux 2.6.16-rc1 - hrtimer hotfix Thomas Gleixner
2006-01-17 20:08   ` Lee Revell
2006-01-17 20:12     ` Thomas Gleixner
2006-01-17 21:06 ` Linux 2.6.16-rc1 Valdis.Kletnieks
2006-01-18  1:41   ` Patrick McHardy
2006-01-17 21:54 ` Eyal Lebedinsky
2006-01-17 23:27   ` Sam Ravnborg
2006-01-18  7:59     ` Jean Delvare
2006-01-18  9:15       ` Sam Ravnborg
2006-01-18 10:01         ` Kurt Wall
2006-01-18 21:10           ` Eyal Lebedinsky
2006-01-19  1:40             ` Kurt Wall
2006-01-18 11:24         ` Eyal Lebedinsky
2006-01-18 12:42           ` Sam Ravnborg
2006-01-18 12:13         ` Jean Delvare
2006-01-18 13:22         ` Jan Engelhardt
2006-01-18 18:12           ` Jean Delvare
2006-01-18 20:14             ` Jan Engelhardt [this message]
2006-01-18 20:32             ` Sam Ravnborg
2006-01-18 20:54               ` Bryan O'Sullivan
2006-01-18 21:20                 ` Sam Ravnborg
2006-01-18 21:47                   ` Bryan O'Sullivan
2006-02-07 12:42                   ` Jean Delvare
2006-02-07 16:55                     ` Bryan O'Sullivan
2006-01-18 16:15         ` Johannes Stezenbach
2006-01-18  8:44     ` Eyal Lebedinsky
2006-01-27  0:06 ` Linux 2.6.16-rc1 - usb printer problems Helge Hafting
2006-01-27 22:52   ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.61.0601182112190.25325@yvahk01.tjqt.qr \
    --to=jengelh@linux01.gwdg.de \
    --cc=eyal@eyal.emu.id.au \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).