This is the mail archive of the
mailing list for the GCC project.
Re: PR18810, darwin don't unlink /dev/null on make install
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Peter O'Gorman <peter at pogma dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Thu, 10 Feb 2005 10:10:32 -0500
- Subject: Re: PR18810, darwin don't unlink /dev/null on make install
- References: <420B6B77.email@example.com>
On Thu, 2005-02-10 at 23:11 +0900, Peter O'Gorman wrote:
> I was getting my /dev/null unlinked when I did make install, I didn't really
> like that.
> There are a number of things at play here. For example, I have no idea why
> make is deciding it needs to rebuild libgcc.a on my system when I do 'sudo
> make install', another is, why does darwin's as have
> in write_object.c, and of course, why does sudo rm /dev/null actually work.
> Could someone please apply this. The output file is named vis_test___out.o
> so it is highly unlikely to conflict with anything that gcc actually needs.
> It is safe to have an output file because we are always going to be in
> $(top_build_dir)/gcc here and that must be writable.
BTW, i can verify that this problem still occurs in 10.4.
It bites me whenever i try to sudo make install into /usr/<someprefix>