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: Documenting tools necessary for GCC [draft]

From: Alexandre Oliva <aoliva at redhat dot com>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Geert Bosch <bosch at gnat dot com>, "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, neil at daikokuya dot co dot uk, gcc at gcc dot gnu dot org, jbuck at synopsys dot com, jsm28 at cam dot ac dot uk
Date: 02 Jun 2003 17:49:15 -0300
Subject: Re: Documenting tools necessary for GCC [draft]
Organization: GCC Team, Red Hat
References: <157BE9E0-93E5-11D7-948C-00039344BF4A@gnat.com><orbrxgmjck.fsf@free.redhat.lsd.ic.unicamp.br><878yskckjk.fsf@egil.codesourcery.com>

On Jun  2, 2003, Zack Weinberg <zack@codesourcery.com> wrote:

> This is pure speculation, but I'm pretty sure most of mklibgcc would
> become unnecessary if we could use GNU make's pattern rules.

It wouldn't be too hard to convince me of this, but ideally libgcc
should be moved into a separate top-level directory and handled by the
generic multilib machinery, which would obviate such pattern rules.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

Follow-Ups:
- Re: Documenting tools necessary for GCC [draft]
  - From: Zack Weinberg

References:
- Re: Documenting tools necessary for GCC [draft]
  - From: Geert Bosch
- Re: Documenting tools necessary for GCC [draft]
  - From: Alexandre Oliva
- Re: Documenting tools necessary for GCC [draft]
  - From: Zack Weinberg

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