All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Eyal Lebedinsky <eyal@eyal.emu.id.au>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.16-rc1
Date: Wed, 18 Jan 2006 13:13:04 +0100	[thread overview]
Message-ID: <20060118131304.23088492.khali@linux-fr.org> (raw)
In-Reply-To: <20060118091543.GA8277@mars.ravnborg.org>

Hi Sam,

> The shell script check-dialog.sh is called which again do:
> echo "main() {}" | gcc -xc - -o /dev/null
> 
> And it seems that gcc will trash /dev/null in your setup when doing
> this.
> One fix would be to avoid the two lines during distclean,
> but I may have to resort to a temporary file.
> 
> Could you please confirm that the above command is the one that trashes
> /dev/null, then I will try to cook up something better.

I confirm that this one line is causing the trouble:

root@arrakis:~> ls -l /dev/null
crw-rw-rw-  1 root root 1, 3 2006-01-18 13:34 /dev/null
root@arrakis:~> echo "main() {}" | gcc -xc - -o /dev/null
root@arrakis:~> ls -l /dev/null
crwxrwxrwx  1 root root 1, 3 2006-01-18 13:34 /dev/null
root@arrakis:~> 

This is with both gcc 3.3.6 from Slackware 10.2 and gcc 4.0.2 from Suse
10.0. Didn't try with self-compiled gcc versions on these systems.

BTW, I have noticed recently an "a.out" file at the root of my linux
sources tree when I build a kernel.

-rwxr-xr-x   1 khali users  11K 2006-01-16 19:51 a.out*

Running it doesn't seem to do anything useful. Is this file generated
here on purpose? Is it somehow related to the current issue?

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2006-01-18 12:12 UTC|newest]

Thread overview: 54+ 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-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 [this message]
2006-01-18 13:22         ` Jan Engelhardt
2006-01-18 18:12           ` Jean Delvare
2006-01-18 20:14             ` Jan Engelhardt
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=20060118131304.23088492.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=eyal@eyal.emu.id.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.