fstack protector

[Stuart Anderson]

On Sat, 19 Apr 2003, Kris Kennaway wrote:

> Hmm, OK.  From the point of view of the FreeBSD port this is a POLA
> violation..it should just use CFLAGS like everything else is supposed
> to.

Well, the modules are a little bit different. They are supposed to be built
in an OS neutral manner, almost a semi cross build setup. Blindly picking up
the hosts CFLAG setting often won't do the right thing, hence the use of a
different VARIABLE name. Note that the default it to set MODCFLAGS to CFLAGS,
but the hook is there for when that is not the right thing to do.

The X build system explicitely sets CFLAGS to a set value in every Makefile.
This is just the way it has been done for 15+ years. The variable CDEBUGFLAGS
can be used to pass in extra stuff. The two options for getting the ports idea
of CFLAGS passed into the build are to either pass it in as CDEBUGFLAGS, or
capture it during the package configuration, and set it in XFree86s host.def
file so it will be built into all of the Makefiles.

This has probably wandered far enough off topic for this list by now 8-).


                                Stuart

Stuart R. Anderson                               anderson at netsweng.com
Network & Software Engineering                   http://www.netsweng.com/
1024D/37A79149:                                  0791 D3B8 9A4C 2CDC A31F
                                                 BD03 0A62 E534 37A7 9149