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 335240 - Wrong compiler options on Solaris using Sun's C compiler
Wrong compiler options on Solaris using Sun's C compiler
Status: RESOLVED NOTGNOME
Product: pygtk
Classification: Bindings
Component: general
2.8.x
Other All
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-20 16:01 UTC by Trond H. Amundsen
Modified: 2006-04-01 22:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Trond H. Amundsen 2006-03-20 16:01:59 UTC 
Please describe the problem:
The configure script wrongly assumes that the compiler understands -std=c9x and
-fno-strict-aliasing options:

checking whether cc-wrapper understands -Wall... no
checking whether cc-wrapper understands -std=c9x... yes
checking whether cc-wrapper understands -fno-strict-aliasing... yes

This results in compiler warnings such as:

cc: Warning: illegal option -d=c9x
cc: Warning: illegal option -fno-strict-aliasing

Not a big issue, just wanted to let you know. It compiles and works just fine.

FWIW, this was Sun Studio 9, Sun C 5.6 2004/07/15

Steps to reproduce:
1. compile pygtk on a solaris box using Sun's C compiler


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Gustavo Carneiro 2006-04-01 22:15:28 UTC 
I checked JH_ADD_CFLAG and it is correct.  It uses AC_TRY_COMPILE from autoconf, which could be where the bug is.