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 309083 - won't build with GCC4 lots of difference in signedness errors
won't build with GCC4 lots of difference in signedness errors
Status: RESOLVED NOTABUG
Product: gnome-build
Classification: Deprecated
Component: miscellaneous
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-build Maintainers List
gnome-build Maintainers List
: 300946 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-06-26 21:11 UTC by Kristof Vansant
Modified: 2005-07-27 17:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kristof Vansant 2005-06-26 21:11:13 UTC 
Please describe the problem:
temperary workaround is:

Index: configure.in
===================================================================
RCS file: /cvs/gnome/gnome-build/configure.in,v
retrieving revision 1.70
diff -u -r1.70 configure.in
--- configure.in        10 Jun 2005 12:32:02 -0000      1.70
+++ configure.in        26 Jun 2005 21:03:31 -0000
@@ -90,7 +90,7 @@
 # Environment
 GNOME_COMMON_INIT
 if test x$MAINT = x; then
-    GNOME_COMPILE_WARNINGS(error)
+    dnl GNOME_COMPILE_WARNINGS(error)
     DEPRECATED_FLAGS="-DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED
-DGTK_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -DBONOBO_DISABLE_DEPRECATED
-DBONOBO_UI_DISABLE_DEPRECATED"
 else
     GNOME_COMPILE_WARNINGS(maximum)


Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Kristof Vansant 2005-07-27 12:02:42 UTC 
*** Bug 300946 has been marked as a duplicate of this bug. ***
Comment 2 Naba Kumar 2005-07-27 17:09:23 UTC 
-Werror flag was given for reason and it only comes into picture when you
compile if from cvs (as opposed to tarbarball/distro). It is to bug the
developer to fix them.

Anyway, the warnings should no longer be there now as I committed a patch that
fixes them.

Thanks.