This is the mail archive of the gcc-patches@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: [patch] Split config.build out from config.gcc

From: Nathanael Nerode <neroden at twcny dot rr dot com>
To: DJ Delorie <dj at redhat dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Fri, 29 Aug 2003 18:46:21 -0400
Subject: Re: [patch] Split config.build out from config.gcc
References: <20030829220750.GA14426@twcny.rr.com> <200308292235.h7TMZi306340@greed.delorie.com>

DJ Delorie wrote:

Alex, DJ, opinions? Is this OK?

I like the idea of breaking config.gcc up, but I really think we
should have one big case with each platform's code grouped by
platform, not multiple cases grouped by feature.  The platform
maintainers will want it that way.  Comments on that?

I intend to keep 'one big case' for the host file. It seemed preferable for the build file to sort differently given that theoretically everything in the build file should be autoconf-detectable. And in fact the two I broke out (whether to use cpio/tar/cp, and the executable extension) probably are detectable.

It's easy enough to do it the other way, and I'll be happy to, if it's preferred.

Follow-Ups:
- Re: [patch] Split config.build out from config.gcc
  - From: Alexandre Oliva

References:
- [patch] Split config.build out from config.gcc
  - From: Nathanael Nerode
- Re: [patch] Split config.build out from config.gcc
  - From: DJ Delorie

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