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: DJ Delorie <dj at redhat dot com>
Cc: gcc at gcc dot gnu dot org
Date: Tue, 10 Jun 2003 12:20:35 -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><87u1axsr8u.fsf@egil.codesourcery.com><200306101851.h5AIpNZ04884@greed.delorie.com>

DJ Delorie <dj@redhat.com> writes:

>> And Cygwin was also mentioned.  But why build it if neither of these
>> things is true?
>
> Why build libstdc++?  Why build newlib?  Why build libvaja?
>
> Because the end user might want to use it, that's why.

If it's not being installed I don't think the end user is using it.

zw

Follow-Ups:
- Re: Why is libiberty built for the target?
  - From: Phil Edwards

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
- Re: Why is libiberty built for the target?
  - From: Zack Weinberg
- Re: Why is libiberty built for the target?
  - From: DJ Delorie

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