Re: [PATCH] c[includes]

[Phil Edwards <pedwards at disaster dot jaj dot com>]

On Mon, Sep 25, 2000 at 02:14:51PM -0700, Benjamin Kosnik wrote:
> > I've been trying to think of the best way for a GCC installation to remember
> > the configure arguments it was given, for use in testing and bug reporting.
> > Maybe another object in libgcc.a, with a single member like __configure_args,
> > with a value of no more than the simple "--foo --bar=baz" string.
> 
> hmmmmmmmmmmmm. Besides what's in the specs file?
> 
> gcc -dumpspecs

Yeah, I thought about that.  The effects are there, but not the causes.
And most newbies wouldn't understand that, or its significance.  (Heck,
I've been looking at specs files on and off for years and still have to
stop and recall the specs language.)

I was thinking something that would permit

   // somefile.c
   #include <stdio.h>

   int main()
   {
       printf ("%s\n", __the_happy_magic_symbol);
   }

to work with no more than

   gcc somefile.c

and produce

   $ ./somefile
   --prefix=/a/b/c --enable-languages=c++ --enable-foo --enable-bar
   --enable-some-really-tricky-feature-that-the-user-will-forget-he-
   enabled-until-we-remind-him --with-gnu-ld --but-without-gnu-as-which-
   is-required-with-the-tricky-enable
   $

And so forth.  :-)


-- 
pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.