This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Why is libiberty built for the target? (was Re: Why does libiberty have to build before a C library?)

From: DJ Delorie <dj at redhat dot com>
To: phil at jaj dot com
Cc: gcc at gcc dot gnu dot org
Date: Tue, 10 Jun 2003 14:40:45 -0400
Subject: Re: Why is libiberty built for the target? (was Re: Why does libiberty have to build before a C library?)
References: <20030610040442.GA26729@nevyn.them.org> <87y90asfmz.fsf@egil.codesourcery.com> <20030610183752.GA9279@disaster.jaj.com>

> With --enable-install-libiberty, the headers are also installed with
> the .a.  This lets end-users make use of libiberty like any other
> library, instead of having to embed the libiberty sources in their
> own project.

But you still have to build it first ;-)

References:
- Why does libiberty have to build before a C library?
  - From: Daniel Jacobowitz
- Why is libiberty built for the target? (was Re: Why does libibertyhave to build before a C library?)
  - From: Zack Weinberg
- Re: Why is libiberty built for the target? (was Re: Why does libiberty have to build before a C library?)
  - From: Phil Edwards

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]