[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Sat, 2005-01-29 at 16:07 +1100, Peter Wang wrote:
> Then I'd say we can't use it yet for the normal case. It's probably
> okay for the --enable-strictwarn (aka. WARNMODE=1) case.
Done for linux, and without a proper gcc version check, with the
attached (one-line) patch .
--
Elias Pschernig
Index: configure.in
===================================================================
RCS file: /cvsroot/alleg/allegro/configure.in,v
retrieving revision 1.86
diff -u -p -r1.86 configure.in
--- configure.in 10 Mar 2005 18:32:54 -0000 1.86
+++ configure.in 6 Apr 2005 16:56:12 -0000
@@ -706,7 +706,7 @@ CFLAGS="$CFLAGS -DALLEGRO_LIB_BUILD"
dnl How to compile C and asm files.
if test -n "GCC"; then
if test "X$allegro_strict_warnings" = "Xyes"; then
- WFLAGS="-Wall -W -Wstrict-prototypes -Wno-unused -Werror"
+ WFLAGS="-Wall -W -Wstrict-prototypes -Wno-unused-parameter -Werror"
else
WFLAGS="-Wall -Wno-unused"
fi