This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Why does libiberty have to build before a C library?
- From: "E. Weddington" <eric at umginc dot net>
- To: Peter Barada <pbarada at mail dot wm dot sps dot mot dot com>
- Cc: neroden at twcny dot rr dot com, gcc at gcc dot gnu dot org
- Date: Tue, 10 Jun 2003 11:00:27 -0600
- Subject: Re: Why does libiberty have to build before a C library?
- References: <3EE5A6B4.27298.22DC6C94@localhost> (eric@umginc.net)
On 10 Jun 2003 at 12:39, Peter Barada wrote:
>
> >The AVR cross toolset apparently is one of the easiest to build, I think,
> >because of having it's own library. From what I've seen on the crossgcc list,
> >targets that use glibc (and possibly newlib) seem to be more difficult to
> >build. Any change that will make building cross toolsets *easier* would be
> >incredibly welcome.
>
> Neither glibc or newlib are the problme. The problem is that gcc
> needs headers to build libgcc that newlib or glibc have to supply.
> You can see how the chicken and egg problem starts since glibc needs a
> compiler to configure to a point to install headers....
>
Thanks for clarifying. I knew of *a* problem, just not quite the specifics. The
end result being, if this situation can be significantly helped in any way it
would certainly make a lot of people happier.
Interestingly, this is where the AVR toolset differs AFAIK. We can build a gcc
(w/ a libgcc) without having to supply headers from avr-libc.
Eric