This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Why is libiberty built for the target? (was Re: Why does libibertyhave to build before a C library?)
- From: DJ Delorie <dj at redhat dot com>
- To: zack at codesourcery dot com
- Cc: gcc at gcc dot gnu dot org, geoffk at apple dot com
- Date: Tue, 10 Jun 2003 12:12:12 -0400
- Subject: Re: Why is libiberty built for the target? (was Re: Why does libibertyhave to build before a C library?)
- References: <20030610040442.GA26729@nevyn.them.org> <87y90asfmz.fsf@egil.codesourcery.com>
> I'd like to ask a deeper question: Why is libiberty built for the
> target? I am not aware of any use whatsoever of the generated
> libiberty.a. Certain libraries want to suck in the C++ demangler but
> they can do it the same way gcc and binutils do, viz. by building an
> .o from the libiberty source.
Well, one answer is "why not?" It's a library. We build it so the
target can use it.
Some targets need it, though, like cygwin.