From: Lou Sanchez/V. B. <bel...@co...> - 2006-11-22 07:44:00
|
Hi, I am trying to build freeglut 2.4.0 debug. I have tried configure --debug (unrecognized option) and configure --enable-debug (compiles with -g but does not link that way). This is on a Fedora Core 5 system. Any help would be appreciated. Cheers Lou |
From: Yuri D'E. <wa...@yu...> - 2006-11-24 09:48:38
|
On 22 Nov 2006, at 08:43, Lou Sanchez/Viviana Bellifemine wrote: > Hi, > I am trying to build freeglut 2.4.0 debug. I have tried configure > --debug (unrecognized option) and configure --enable-debug (compiles > with -g but does not link that way). This is on a Fedora Core 5 > system. > Any help would be appreciated. There is one proper way: CFLAGS="-g $CFLAGS" LDFLAGS="-g $LDFLAGS" ./configure Configure flags like --debug should *never* set any compiler flags. |
From: Lou Sanchez/V. B. <bel...@co...> - 2006-11-25 07:41:03
|
Hi, Yuri D'Elia wrote: > On 22 Nov 2006, at 08:43, Lou Sanchez/Viviana Bellifemine wrote: > >> Hi, >> I am trying to build freeglut 2.4.0 debug. I have tried configure >> --debug (unrecognized option) and configure --enable-debug (compiles >> with -g but does not link that way). This is on a Fedora Core 5 >> system. >> Any help would be appreciated. >> > There is one proper way: > > CFLAGS="-g $CFLAGS" LDFLAGS="-g $LDFLAGS" ./configure > > Configure flags like --debug should *never* set any compiler flags. > Why? Is there a style or philosophy guide somewhere? It seems like compiler dependencies (such as -g for debug) is what autoconf is there to eliminate. > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Freeglut-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freeglut-developer > Cheers Lou |
From: Yuri D'E. <wa...@yu...> - 2006-11-25 10:53:21
|
On 25 Nov 2006, at 08:40, Lou Sanchez/Viviana Bellifemine wrote: >> There is one proper way: >> >> CFLAGS="-g $CFLAGS" LDFLAGS="-g $LDFLAGS" ./configure >> >> Configure flags like --debug should *never* set any compiler flags. >> > Why? Is there a style or philosophy guide somewhere? It seems like > compiler dependencies (such as -g for debug) is what autoconf is there > to eliminate. Because there's not a single "debug" flag, like there's no single "optimization" flag: that's the main reason CFLAGS/etc are exposed to the user. autoconf scripts must never try to fiddle with flags directly because every compiler considers them in a different way (yes, -g and -O included), with the only exception being extra libraries or paths. On your build, you might want to activate profiling, generate code coverage, use a malloc debugger, etc, something like -ggdb3 -pg - fprofile-arcs -lefence. None of these flags is portable, none of these has anything to do with project configuration and finally every user may need something different (enabling "-g" with the default CFLAGS may be useless if CFLAGS contains some overrides and/or certain optimization flags depending on the compiler). If present, an "--enable-debug" flag should enable extra debugging *code* (like assertions, traces, or self-checks). You might want to have this code enabled with or without debugging symbols. Autoconf is no substitute to compiler and platform documentation. Autoconf does not automatically make your program portable. These are common misconceptions, in fact most autoconf-based packages are not portable at all. I wished there was a decent guide in autoconf, which would list the things to do, the things to avoid, how to use configure scripts effectively, etc, but AFAIK, all the documentation surrounding autotools is and has always been incredibly poor. Even the autotools book, which is targeted to developers, is completely useless for several reasons (which I will list if you ask). So no... I don't think there's a philosophy guide until you hit the problem and learn the lesson yourself. Hope this helps. |