Yeah, the Ports system passes global CFLAGS in so system specific optimizations and other such things can occur.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-cflags.html After reading Clodoaldo's response earlier I implemented a solution to add "-Wc," to options that don't have a "-W?" prefix. However, upon further inspection it looks like you can just pass all of CFLAGS in one option (-Wc,"$(CFLAGS)"). Perhaps that is the way to go? Thanks! -- Douglas William Thrift <[email protected]> <http://douglasthrift.net/> Graham Dumpleton wrote: > Is it some policy with FreeBSD builds that it always supplies some > arbitrary set of CFLAGS in the environment of the 'configure' script > to try and enforce some particular compiler options? > > This would only fail if CFLAGS is being set. Previously they would > have been ignored. > > Clodoaldo rightly points out the issue: > > http://code.google.com/p/modwsgi/issues/detail?id=166 > > with the original issue where someone asked for the change being: > > http://code.google.com/p/modwsgi/issues/detail?id=164&can=1&start=100 > > When using CFLAGS was added, that original person didn't report an > issue around needing to use -Wc, as prefix to arguments. > > As mentioned in subsequent report about it, as I say, automatically > adding -Wc, with mod_wsgi configure script can be a bit of a problem > in itself. > > I need to do some research on how other Apache modules with configure > scripts handle this unless someone else already knows of a full proof > scheme. Any scheme needs to deal with options already having -Wc, > prefix. Values to options with quoted strings having spaces etc. > Although, for the latter no one should be setting such problematic > options for mod_wsgi I guess. > > All I know is I got tripped up really badly at one point when trying > to do similar -Wl, fiddles in LDFLAGS. > > Graham > > 2009/11/22 Douglas Thrift <[email protected]>: >> Wow! >> >> So I decided to start working on upgrading the FreeBSD port to 2.7 >> before figuring out what to do about 3.0. And I got the following: >> >> [doug...@slowhand:mod_wsgi]$ make >> ===> Extracting for mod_wsgi-2.7 >> => MD5 Checksum OK for mod_wsgi-2.7.tar.gz. >> => SHA256 Checksum OK for mod_wsgi-2.7.tar.gz. >> ===> Patching for mod_wsgi-2.7 >> ===> mod_wsgi-2.7 depends on file: /usr/local/bin/python2.6 - found >> ===> mod_wsgi-2.7 depends on file: /usr/local/sbin/apxs - found >> ===> Configuring for mod_wsgi-2.7 >> checking Apache version... 2.2.13 >> configure: creating ./config.status >> config.status: creating Makefile >> ===> Building for mod_wsgi-2.7 >> /usr/local/sbin/apxs -c -I/usr/local/include/python2.6 -DNDEBUG >> -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x20000 -O2 -fno-strict-aliasing >> -pipe -march=nocona mod_wsgi.c -L/usr/local/lib >> -L/usr/local/lib/python2.6/config -lpython2.6 -lutil -lm >> apxs:Error: Unknown option: O. >> apxs:Error: Unknown option: 2. >> apxs:Error: Unknown option: f. >> apxs:Error: Unknown option: m. >> apxs:Error: Unknown option: r. >> apxs:Error: Unknown option: h. >> apxs:Error: Unknown option: =. >> Usage: apxs -g [-S <var>=<val>] -n <modname> >> apxs -q [-S <var>=<val>] <query> ... >> apxs -c [-S <var>=<val>] [-o <dsofile>] [-D <name>[=<value>]] >> [-I <incdir>] [-L <libdir>] [-l <libname>] [-Wc,<flags>] >> [-Wl,<flags>] [-p] <files> ... >> apxs -i [-S <var>=<val>] [-a] [-A] [-n <modname>] <dsofile> ... >> apxs -e [-S <var>=<val>] [-a] [-A] [-n <modname>] <dsofile> ... >> *** Error code 1 >> 1 error >> *** Error code 1 >> >> Stop in /home/douglas/ports/www/mod_wsgi. >> >> Not sure what's going on here. :( >> >> Thanks! >> -- >> Douglas William Thrift >> <[email protected]> >> <http://douglasthrift.net/> >> >> Graham Dumpleton wrote: >>> Have fun. >>> >>> http://code.google.com/p/modwsgi/wiki/ChangesInVersion0207 >>> http://code.google.com/p/modwsgi/wiki/ChangesInVersion0300 >>> >>> Version 3.0 is same as last release candidate exception for version >>> string embedded within it. >>> >>> Version 2.7 is just to get out what changes had been sitting in 2.X branch. >>> >>> Graham >>> >>> -- >>> >>> You received this message because you are subscribed to the Google Groups >>> "modwsgi" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/modwsgi?hl=. >>> >>> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "modwsgi" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/modwsgi?hl=. >> >> >> > > -- > > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=. > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=.
