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 does libiberty have to build before a C library?

From: DJ Delorie <dj at redhat dot com>
To: drow at mvista dot com
Cc: gcc at gcc dot gnu dot org
Date: Tue, 10 Jun 2003 13:11:16 -0400
Subject: Re: Why does libiberty have to build before a C library?
References: <20030610040442.GA26729@nevyn.them.org> <87adcqa2r3.fsf@fleche.redhat.com> <20030610135606.GA496@nevyn.them.org> <200306101617.h5AGHHw32738@greed.delorie.com> <20030610164150.GA5158@nevyn.them.org> <200306101703.h5AH3CV03093@greed.delorie.com> <20030610170604.GA5717@nevyn.them.org>

> I guess the question is:
>   does libiberty provide things missing from newlib on cygwin, or does
>   newlib use libiberty during its build process?

winsup pulls in libiberty to pick up the extra functions.

Follow-Ups:
- Re: Why does libiberty have to build before a C library?
  - From: Daniel Jacobowitz

References:
- Why does libiberty have to build before a C library?
  - From: Daniel Jacobowitz
- Re: Why does libiberty have to build before a C library?
  - From: Tom Tromey
- Re: Why does libiberty have to build before a C library?
  - From: Daniel Jacobowitz
- Re: Why does libiberty have to build before a C library?
  - From: DJ Delorie
- Re: Why does libiberty have to build before a C library?
  - From: Daniel Jacobowitz
- Re: Why does libiberty have to build before a C library?
  - From: DJ Delorie
- Re: Why does libiberty have to build before a C library?
  - From: Daniel Jacobowitz

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