This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Why does gcc's Makefile have so many targets?
- From: Ian Lance Taylor <iant at google dot com>
- To: NightStrike <nightstrike at gmail dot com>
- Cc: gcc-help <gcc-help at gcc dot gnu dot org>
- Date: 20 Feb 2008 19:07:48 -0800
- Subject: Re: Why does gcc's Makefile have so many targets?
- References: <b609cb3b0802161914o3ffa8040i6ffceac90d75890e@mail.gmail.com>
NightStrike <nightstrike@gmail.com> writes:
> I noticed that the Makefile for gcc can compile many many things,
> including sed, ash, dosutils, gawk, uudecode, and perl, just to name a
> few. What is the purpose for this? How is this done if none of those
> things are in the gcc svn repository?
This is a historical legacy of the Cygnus configure script, retained
because some people do like to build at least the binutils, newlib,
and gdb in the same source tree as gcc (this is sometimes called the
combined tree build or the uberbaum build). There is some historical
background at http://airs.com/ian/configure/ .
Ian