This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Building collect2 for C?
- From: "E. Weddington" <eric at ecentral dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 16 Mar 2004 16:02:52 -0700
- Subject: Re: Building collect2 for C?
On 16 Mar 2004 at 15:52, DJ Delorie <dj@redhat.com> wrote:
> On 16 Mar 2004 at 17:44, DJ Delorie wrote:
>
> >
> > > Because I'm building a cross-compiler:
> > > --host=mingw32
> > > --build=mingw32
> > > and target != host
> >
> > You should have GNU ld in this case,
>
> Yes.
>
> though, assuming your target is
> > supported by GNU ld.
>
> Yes.
>
> > Why is collect2 needed *at all*?
>
> *Exactly* the same question I asked that started this thread. :-)
>
> I know I have GNU ld and that the target supports GNU ld, because I'm using the
> Cygwin environment to build in (building the cross compiler with CC="gcc -mno-
> cygwin") and there are two separate targets that I'm interested in building: avr
> and m68k-elf. And I know that this issue has existed at least for 1.5 years on
> the avr.
[Slightly OT]
... And before anyone goes off and says that "I should just build with Cygwin
and be done with it", there are very valid reasons to build a toolset that does
not link to the Cygwin DLL, mainly having to do with redistribution of the
executables and versioning issues with that DLL. Building a completely native
Win32 toolset is very desirable in many cases and that's what I'm trying to do
with two different toolsets.
Eric