Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Do not enable _FORTIFY_SOURCE without optimization | Allan McRae | 2012-08-01 |
| | | | | | | | | | | | | | | With glibc-2.16, using -D_FORTIFY_SOURCE requires that optimization (-O) be used or it will prodice a warning message. Enable -Werror in our test for _FORTIFY_SOURCE support to catch when a users specifies CFLAGS without optimization. The line to set CFLAGS="" when no CFLAGS are specified (either due to being unset or geniunely empty) is required as autoconf will use "-O2 -g" for its tests by defult when CFLAGS is unset, but will not add them to the CFLAGS used... Signed-off-by: Allan McRae <allan@archlinux.org> | ||
* | Define _FORTIFY_SOURCE in CPPFLAGS | Allan McRae | 2012-05-20 |
| | | | | | | | The -D_FORTIFY_SOURCE=2 define should be in CPPFLAGS and not CFLAGS Signed-off-by: Allan McRae <allan@archlinux.org> Signed-off-by: Dan McGee <dan@archlinux.org> | ||
* | Add a new configure option for excessive compiler warning flags | Dan McGee | 2012-04-08 |
| | | | | | | This adds a bunch of warning flags to the list used when compiling. Signed-off-by: Dan McGee <dan@archlinux.org> | ||
* | buildsys: move acinclude.m4 to m4/ | Dave Reisner | 2012-04-08 |
Signed-off-by: Dave Reisner <dreisner@archlinux.org> |