This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
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:05:19 -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>
Alexandre Oliva <aoliva@redhat.com> writes:
>> Another issue that we found with the GNAT front end, is that with
>> the extra GNU make features one doesn't need to rely as much on shell
>> capabilities.
>
> You mean GNU make functions? I'd much rather not start depending on
> them. I can see sometimes there may be benefits to doing so, but it
> pretty much makes us entirely dependent on GNU make. I could live
> with that if the benefits are clearly worth it, but I don't want us to
> use GNU make features just because we can.
This is pure speculation, but I'm pretty sure most of mklibgcc would
become unnecessary if we could use GNU make's pattern rules.
zw