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] fixincludes to the toplevel: toplevel changes

From: Nathanael Nerode <neroden at twcny dot rr dot com>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: DJ Delorie <dj at redhat dot com>, gcc-patches at gcc dot gnu dot org
Date: Mon, 30 Aug 2004 15:43:22 -0400
Subject: Re: [PATCH] fixincludes to the toplevel: toplevel changes
References: <41335B0F.6060205@gnu.org> <200408301755.i7UHtV5D023379@greed.delorie.com> <41337BF4.4070408@twcny.rr.com> <87isb077h4.fsf@codesourcery.com>

Zack Weinberg wrote:

Nathanael Nerode <neroden@twcny.rr.com> writes:
(c) [libiberty] is in fact the *only* module which is built both for
the host and for the build machine (and I would expect that to
remain true)
libcpp is about to become another such module.

Weird. Why? We already rely on having a preexisting ISO C90 cpp on the build machine...

...aha! Is it (partially) automatic dependency generation for C? And you want to get dependencies on target-specific and conditionally included files, so you have to have it run at build time?...

Did I guess right?

Follow-Ups:
- Re: [PATCH] fixincludes to the toplevel: toplevel changes
  - From: Daniel Jacobowitz
- Re: [PATCH] fixincludes to the toplevel: toplevel changes
  - From: Zack Weinberg

References:
- [PATCH] fixincludes to the toplevel: toplevel changes
  - From: Paolo Bonzini
- Re: [PATCH] fixincludes to the toplevel: toplevel changes
  - From: DJ Delorie
- Re: [PATCH] fixincludes to the toplevel: toplevel changes
  - From: Nathanael Nerode
- Re: [PATCH] fixincludes to the toplevel: toplevel changes
  - From: Zack Weinberg

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