pacman - Archlinux32 fork of pacman

Age	Commit message (Collapse)	Author
2014-01-06	Remove -fgnu89-inline from compile options	Dan McGee
	This was a hack done by me in commit d8e88aa0175fd back in 2007 that is no longer necessary, given a sufficiently smart compiler and one that supports the inline keyword. Signed-off-by: Dan McGee <dan@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org>
2013-02-13	Fix --enable-warningflags	Allan McRae
	gcc gives an error on an unknown warning flag, but clang just gives a warning. Upgrade the warning in clang to an error by activating -Werror=unknown-warning-option if available. Signed-off-by: Allan McRae <allan@archlinux.org>
2012-11-27	Fix typo in acinclude.m4 fs_old_*flags	Dan McGee
	Introduced in commit d2669b47. Signed-off-by: Dan McGee <dan@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org>
2012-08-01	Do not enable _FORTIFY_SOURCE without optimization	Allan McRae
	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>
2012-05-20	Define _FORTIFY_SOURCE in CPPFLAGS	Allan McRae
	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>
2012-04-08	Add a new configure option for excessive compiler warning flags	Dan McGee
	This adds a bunch of warning flags to the list used when compiling. Signed-off-by: Dan McGee <dan@archlinux.org>
2012-04-08	buildsys: move acinclude.m4 to m4/	Dave Reisner
	Signed-off-by: Dave Reisner <dreisner@archlinux.org>