Jeff Janes <[email protected]> writes: > I am building from a git checkout. > > After running ./bootstrap, the resulting "./configure --help" advertises a > --disable-debug option. To me this suggests that debugging symbols are > included by default. But they are not, there are no debugging symbols in > the resulting binary, i.e. no line numbers when using gdb. > > the ./configure script also accepts --enable-debug (but does not advertise > it in help), but that option doesn't do anything, at least not for gcc. > > I've found that I can get debuggings symbols by manually forcing it, using: > > make CFLAGS='-g -O2 -Wall' > > But this should not be necessary. There seems to be some bug in the system > that generates the ./configure file. But I am not familiar with that > system. Before I try to dig into and figure out what is going, does anyone > have any words of wisdom?
I think this name is misleading. The --enable-debug flag to the configure script flag in fact will define ENABLE_DEBUG that is used by wget internally to support --debug. The way to generate debugging symbols is as you said to pass -g to CFLAGS. Cheers, Giuseppe
