How to configure GCC as debuggable

[Bernd Feindt]

Giovanni Bajo wrote:

> Doing just a regular "make"
> will build you a working GCC in one stage.

This was what I was unsure about. I thought the default configuration was
for end-users and there was some magic necessary to build a
development-version. Just trying out "make" had solved this uncertainty, but
long lasting build processes in the past (say Qt/KDE) prevented me from
playing around. After all the whole built with "--enable-languages=c,c++"
took only about 6 minutes @centrino 1,4 GHz / 512 MB.

> For instance, when I work on the C++ FE,
> I usualy touch cp/cp-tree.h

What is C++ FE?

-----
Dave Korn wrote:

> Say, do we support "configure --help" in the source directory?  > <g>  [
Sorry Bernd.  Gcc in-joke.  Please ignore! ]

Please inaugurate me! ;)

> CFLAGS='-g -O0'

That was a big help for me! "export CFLAGS='-g -O0' CXXFLAGS=$CFLAGS
CFLAGS_FOR_TARGET=$CFLAGS" did it. "configure" then produces a corresponding
makefile, except for "CFLAGS_FOR_TARGET". What is it's purpose? Is it
considered by make as an environment variable?

-----
Phil Edwards wrote:

> building with -g3 lets you use
> preprocessor macros

Thank you! I earlier read that some gdb "macro" commands are not yet
implemented and thought macros are generally missing. That helps A LOT in
understanding the syntax tree structures.

-----
THANK YOU ALL for your great, fast answers to my questions. I had big
troubles in understanding the C++-parser until now, but now I can follow the
control flow and see what is going on there at last.

BF.

-- 
GMX ProMail mit bestem Virenschutz http://www.gmx.net/de/go/mail
+++ Empfehlung der Redaktion +++ Internet Professionell 10/04 +++