This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH - ping] Don't unlink /dev/null on darwin
- From: Daniel Jacobowitz <drow at false dot org>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: Peter O'Gorman <peter at pogma dot com>, gcc-patches at gcc dot gnu dot org
- Date: Mon, 14 Feb 2005 13:43:09 -0500
- Subject: Re: [PATCH - ping] Don't unlink /dev/null on darwin
- References: <4210B1A0.80907@pogma.com> <87psz3qayf.fsf@codesourcery.com>
On Mon, Feb 14, 2005 at 09:59:36AM -0800, Zack Weinberg wrote:
> The second patch is a possible general stopgap to prevent this sort of
> scenario from causing damage in the future. It is a very big hammer,
> and I recognize that it may break stuff, but I am nonetheless deadly
> serious about proposing it. It is not ready for inclusion as is - it
> may well be in the wrong place (Peter, if you feel like it, I'd
> appreciate your experimenting to see whether or not it prevents the
> Darwin assembler from unlinking /dev/null if you run the problem
> command by hand as root) and it certainly needs autoconf goo. Right
> now, though, what I want to hear about is not these minor details, but
> rather compelling reasons why we should *not* do this, because I can't
> think of any.
I think that forbidding gcc from running as root is a hideously bad
idea. That's site policy. And it will break everyone else's make
install that runs gcc. And it will break lots of Debian package builds
because fakeroot will trigger it.
--
Daniel Jacobowitz
CodeSourcery, LLC