GCC 4.4 landed in rawhide yesterday and I just tried building it using the
autotools build stuff.
Based on how far it got before getting bounced with an error, I think there
will be a lot less stuff caught than during the 4.2 to 4.3 change.
Is this stuff that should get cleaned up for 1.5/1.6 or do people want to
wait until development starts again?
Note that Fedora will be using gcc 4.4 for F11 and if the Wesnoth schedule
doesn't slip too much, 1.6 will be in F11.
For an example here is the first warning/error that I tripped over:
g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include -I/usr/include/pango-1.0
-I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12
-DHAVE_REVISION -I../intl -I../intl -I/usr/include/SDL -D_GNU_SOURCE=1
-D_REENTRANT -DWESNOTH_PATH=\"/home/wesnoth/wesnoth-1.5/share/wesnoth\"
-DLOCALEDIR=\"translations\" -DHAS_RELATIVE_LOCALEDIR=1
-DFIFODIR=\"/home/wesnoth/wesnoth-1.5/var/run/wesnothd\"
-DWESNOTH_PREFIX=\"/home/wesnoth/wesnoth-1.5\" -DHAVE_PYTHON
-I/usr/include/python2.6 -O2 -W -Wall -ansi -g -DDEBUG -Werror -Wno-unused
-Wno-sign-compare -DDISABLE_POOL_ALLOC -D_X11
-DPREFERENCES_DIR=\".wesnoth-1.5\" -I/usr/include -MT ai.o -MD -MP -MF
$depbase.Tpo -c -o ai.o ai.cpp &&\
mv -f $depbase.Tpo $depbase.Po
cc1plus: warnings being treated as errors
ai.cpp: In member function ‘virtual void
ai::analyze_potential_recruit_movements()’:
ai.cpp:1905: error: dereferencing pointer ‘<anonymous>’ does break
strict-aliasing rules
/usr/lib/gcc/i386-redhat-linux/4.4.0/../../../../include/c++/4.4.0/bits/stl_tree.h:259:
note: initialized from here
make[2]: *** [ai.o] Error 1
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev
