This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH RFC: Remove fork from collect2
- From: Ian Lance Taylor <ian at wasabisystems dot com>
- To: Dale Johannesen <dalej at apple dot com>
- Cc: Andrew Pinski <apinski at apple dot com>, "gcc at gcc dot gnu dot org list" <gcc at gcc dot gnu dot org>, Caroline Tice <ctice at apple dot com>
- Date: 19 Mar 2004 17:59:51 -0500
- Subject: Re: PATCH RFC: Remove fork from collect2
- References: <20040317023814.10143.qmail@gossamer.airs.com><20040317092131.GA95030@lorien.int.gecko.de><m3smg7r5cw.fsf@gossamer.airs.com><20040317133116.GA15850@lorien.int.gecko.de><m3k71jr29k.fsf@gossamer.airs.com><20040317170336.GA16667@lorien.int.gecko.de><87d67bw7bd.fsf@egil.codesourcery.com><m3vfl3kyfr.fsf@gossamer.airs.com><A7570576-79EC-11D8-9F81-000393BB90B6@apple.com><009F425B-79EE-11D8-92E2-00039372607E@apple.com><m38yhw4gai.fsf@gossamer.airs.com><0ECB936F-79F8-11D8-A952-000A95D7CD40@apple.com>
Dale Johannesen <dalej@apple.com> writes:
> However, as I said, I don't think that's a general solution to the
> problem.
> Indeed, any solution that makes use of the fact that Apple's system
> compiler happens to be gcc is not the right approach IMO.
I don't think it's a general problem. What's odd here is that the
system compiler is requiring a library which gcc doesn't link against.
That is uncommon. Usually we just make gcc link against the
appropriate libraries, by putting them in LIB_SPEC.
> What's wrong with building libiberty on each pass through the bootstrap?
> That would solve the general problem, and that library builds very
> quickly.
I see nothing wrong with this. It's just tedious to implement. The
bootstrap operation currently executes entirely within the gcc
directory.
Ian