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: Zack Weinberg <zack at codesourcery dot com>
To: Alexandre Oliva <aoliva at redhat 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: Mon, 02 Jun 2003 13:53:04 -0700
Subject: Re: Documenting tools necessary for GCC [draft]
References: <157BE9E0-93E5-11D7-948C-00039344BF4A@gnat.com><orbrxgmjck.fsf@free.redhat.lsd.ic.unicamp.br><878yskckjk.fsf@egil.codesourcery.com><orbrxgkxx0.fsf@free.redhat.lsd.ic.unicamp.br>

Alexandre Oliva <aoliva@redhat.com> writes:

> 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.

Yeah, I'd like to see that done, too.

zw

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

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