output messages

kevin diggs diggskevin38@gmail.com
Tue Nov 16 21:01:00 GMT 2010


On Tue, Nov 16, 2010 at 12:20 PM, Ian Lance Taylor <iant@google.com> wrote:
> kevin diggs <diggskevin38@gmail.com> writes:
>
>> I would like to add some messages into the build stream. Things like:
>>
>> *** Beginning libgcc ... ***
>> *** Beginning libjava ... ***
>>
>> Something easy to locate in a log.
>
> I already see lines like
>
> make[3]: Entering directory `/home/iant/gcc/bootstrap/x86_64-unknown-linux-gnu/libgcc'
>
> That seems sufficient to me.
>
Yea, I see these too. But there are a lot of them. And they require
one to clearly understand gcc structure to know what is getting built
where (or when?). Is the 'production' (i.e. the one that gets
installed) libgcc built in the same place as the one(s) used during
the bootstrap stages? And static versus dynamic?

>> Can someone more familiar with the GCC build system make some
>> suggestions. Where to put them? Makefile.{in,am,tpl (tpl???)}? Maybe a
>> code fragment.
>
> Top level Makefile.tpl.  As the comment at the top of that file
> indicates, you generate Makefile.in from Makefile.tpl and Makefile.def
> using autogen.
>
Ain't not no autogen on this system. What is it? A successor to automake?

>> I can't even get rid of debug information for a 4.3.5 build.
>
> If bootstrapping:
>    make BOOT_CFLAGS="-O2"
> If not bootstrapping (i.e., building a cross-compiler):
>    make CFLAGS="-O2"
>
I have admittedly been hacking and chopping on various configure
script and Makefile parts and could have messed something up ... but
.....

Wait I have been defining these only when I run configure. Are you
saying I need to pass them on the actual make command?

Any thoughts on adding support for the configure machinery
{--enable-|--disable-}feature option for debug:   --disable-debug.
This would save people the hassle of trying to remember when to omit
-g and from what to omit it from?

Latest 4.3.5 is 474508 KiB and took 1003 minutes. No Ada and no obj-c++.

Thanks for your time!

kevin



More information about the Gcc-help mailing list