passing FLAGS_FOR_TARGET_ to subdirectories
Nathanael Nerode
neroden@doctormoo.dyndns.org
Mon Oct 28 19:50:00 GMT 2002
On Mon, Oct 28, 2002 at 09:02:12PM -0500, Daniel Jacobowitz wrote:
> On Mon, Oct 28, 2002 at 07:48:53PM -0500, Nathanael Nerode wrote:
> > I just read http://gcc.gnu.org/ml/gcc-patches/2002-10/msg01720.html.
> >
> > I don't like it at all. It's ugly and it introduces an extra temporary
> > file. It significantly complicates my goal, which is to clean up
> > the configure and build process; this goes in the opposite
> > direction. Don't do it, or I'll be forced to propose a patch that
> > removes it. :-P
>
> How would you do it then? I think it's cleaner, personally. When the
> top level is autoconfed, I'd turn the use of the temporary file into
> dropping them into config.cache, and error in the subdirs if the value
> isn't already cached. I didn't want to blit data into config.cache
That would be OK (even elegant), although I would prefer not to error in
the subdirs; I don't see why a hard error would be necessary.
> from a non-autoconf script.
So wait until I've autoconfiscated. If gcc 3.3 would BRANCH ALREADY
we'd be autoconfiscated (although there would be further cleanup I
wanted to do) within a month, I estimate. Is this fixing a
release-critical bug? Then do it in a branch release.
OK, sorry, I'm getting irritable because my patches are delayed through
no fault of my own. Not your fault either.
> I can't pass them in the command line or in the environment. They have
> to go somewhere.
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
More information about the Gcc-patches
mailing list