After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 578983 - set_more_warnings check of WARNING_CFLAGS doesn't work
set_more_warnings check of WARNING_CFLAGS doesn't work
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: [obsolete] Builds
0.x.x [obsolete]
Other opensolaris
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-04-14 21:46 UTC by James Andrewartha
Modified: 2009-04-16 13:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description James Andrewartha 2009-04-14 21:46:15 UTC 
I'm building nautilus from SVN HEAD with gcc 3.4.3, which doesn't have -Wno-pointer-sign. The code in configure.in that checks if gcc understands the option doesn't work - config.log has:
configure:28253: checking for more warnings
configure:28256: result: yes
configure:28268: checking whether gcc understands -Wstrict-aliasing=0
configure:28291: gcc -c -g -O2  conftest.c >&5
configure:28298: $? = 0
configure:28315: result: yes
configure:28268: checking whether gcc understands -Wno-pointer-sign
configure:28291: gcc -c -g -O2  conftest.c >&5
configure:28298: $? = 0
configure:28315: result: yes
so WARNING_CFLAGS isn't being passed to gcc so the flag isn't actually tested.
Comment 1 Alexander Larsson 2009-04-16 13:18:51 UTC 
2009-04-16  Alexander Larsson  <alexl@redhat.com>

	Bug 578983 – set_more_warnings check of WARNING_CFLAGS doesn't work
	
	* configure.in:
	Actually check the options.