Matthew Lye wrote: > Well, apparently someone rolled a natural 20 on precog. > > Currently spotted problems: > 1) cflags are defined as the "additional" cc flags, rather than the > optimizer/debugger flags, which are now "-O". Not sure what effect > this will have.
It should only use -O if it didn't recognize GCC or if you're using something older than GCC 3.x. -O means "optimize" for pretty much all C compilers, whereas -O2 and others are more GCC-specific. If you pass your own compiler flags via CFLAGS or --cflags=, these will override clashing compiler options more left on the command-line. Thus, if you see "-O -O2", -O2 will be used. I know it looks a bit ugly with the duplicate compiler flags and I'll fix that later but it's rather cosmetic than a real problem. > 2) my little attempt to hack the "$so" variable (suffix) failed, yes. Retry with the current build.sh please. If "$so" is still necessary, I'll let it default to "dylib" if "uname -s" gains "darwin" or whatever. > 3) Desperately need a method to remove "-Wshadow" (warn about > shadowing) from the list of cc flags. Is this ever put to good use? > Should it be a default? You can use -Wno-shadow. As the flags are appended to the default and GCC let's the last one win, that'll disable any shadow warnings. -Wshadow is useful, yes, I found at least one significant bug with it and in general it just prevents that you even think about recycling identifiers keeping the code cleaner. Of course, it's just one of thousands little useful things which are nice to have. -- Christian ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
