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: tromey at redhat dot com, geoffk at apple dot com, gcc at gcc dot gnu dot org
Date: Tue, 10 Jun 2003 12:17:17 -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>

> 2003-05-21  DJ Delorie  <dj@redhat.com>
>         
>         * Makefile.tpl (configure-target-libiberty): Depend only on gcc, not
>         newlib or libgloss.
>         * Makefile.in: Regenerate.
> 
> DJ, that's pretty recent - could you explain why it was done?

If you add that dependency, it creates a dependency loop and the build
fails.  I can dig up the old emails about it, but they were right
around the time of the patch.

Note that any dependencies between modules must be explicitly
specified via Makefile dependencies now.  Please do not rely on the
order that they're listed - I can pretty much guarantee that that will
NOT work any more.

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

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