public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: proton <proton@energymech.net>
To: linux-kernel@vger.kernel.org
Subject: Makefile gcc -o /dev/null: the dissapearing of /dev/null
Date: Sat, 29 Sep 2001 09:55:35 +0200	[thread overview]
Message-ID: <3BB57E77.4CDFF5D0@energymech.net> (raw)

I noticed this a long time ago in the Linux kernel
makefiles, I thought someone would have figured it
out by now tho.

The `gcc -o /dev/null' is a really neat way of
testing if gcc works or not.

Unfortunatly it doesnt work that well if you're root.

You see, gcc uses unlink(). /dev/null doesnt take
kindly to that kind of treatment...

Ofcourse, you cant unlink /dev/null unless you are root.

In any case, the `gcc -o /dev/null' test cases probably
need to go away.

I've seen this in linux/arch/i386/Makefile for 2.4.10,
it probably exists in all previous versions as well as
in other Makefiles.

Happy kernel hacking!

/proton
ps. any replies [read: flames] would do well being CC'd
to me since I dont subscribe to linux-kernel :)
[ http://www.energymech.net/users/proton/ ]

             reply	other threads:[~2001-09-29  7:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-29  7:55 proton [this message]
2001-09-29  9:43 ` Makefile gcc -o /dev/null: the dissapearing of /dev/null Jan-Benedict Glaw
2001-09-29 13:10   ` Jim Treadway
2001-09-29 18:21     ` Jan-Benedict Glaw
2001-09-30  3:03       ` Jim Treadway
2001-10-01 14:46       ` Rob Landley
2001-09-29 18:36     ` J.H.M. Dassen (Ray)
2001-09-30 14:24     ` Olaf Titz
2001-09-30 23:47       ` Jim Treadway

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=3BB57E77.4CDFF5D0@energymech.net \
    --to=proton@energymech.net \
    --cc=linux-kernel@vger.kernel.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