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?

From: Zack Weinberg <zack at codesourcery dot com>
To: Phil Edwards <phil at jaj dot com>
Cc: gcc at gcc dot gnu dot org, dj at redhat dot com, geoffk at apple dot com
Date: Tue, 10 Jun 2003 11:48:49 -0700
Subject: Re: Why is libiberty built for the target?
References: <20030610040442.GA26729@nevyn.them.org><87y90asfmz.fsf@egil.codesourcery.com><20030610183752.GA9279@disaster.jaj.com>

Phil Edwards <phil@jaj.com> writes:

> On Mon, Jun 09, 2003 at 09:47:16PM -0700, Zack Weinberg wrote:
>> 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.
>
> 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.

And Cygwin was also mentioned.  But why build it if neither of these
things is true?

zw

Follow-Ups:
- Re: Why is libiberty built for the target?
  - From: DJ Delorie

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]