This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Libiberty issue vs cygwin [was Re: This is a Cygwin failure yeah?]
- From: DJ Delorie <dj at redhat dot com>
- To: "Dave Korn" <dave dot korn dot cygwin at googlemail dot com>
- Cc: gcc at gcc dot gnu dot org, kirkshorts at googlemail dot com
- Date: Fri, 16 Jan 2009 01:20:53 -0500
- Subject: Re: Libiberty issue vs cygwin [was Re: This is a Cygwin failure yeah?]
- References: <2ca21dcc0901152026k2c30822epa891e6c4f9efdd30@mail.gmail.com>
IIRC, that whole clause was because cygwin's dll itself linked with
libiberty, so the auto-detect stuff needed an override to make sure
the right files were there when you build cygwin1.dll. Otherwise, it
would detect that cygwin had strsignal, not build it, then fail later
when cygwin1.dll couldn't find strsignal.
If cygwin no longer links with libiberty, that whole clause can
probably go away now. As it's target-specific, I'm OK with letting
the target maintainers have the last word about it, too.