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 113992 - compile failure with gcc-3.3
compile failure with gcc-3.3
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: 0.6.x
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 113993 114002 (view as bug list)
Depends on: 108699
Blocks:
 
 
Reported: 2003-05-29 19:49 UTC by David Schleef
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Schleef 2003-05-29 19:49:20 UTC 
Gstreamer does not compile with -Wall -Werror with gcc-3.3 because of a bug
in glib (#113991).

Workarounds:

 1) Don't use gcc-3.3 by running 'CC=gcc-3.2 ./autogen.sh'

 2) Remove -Werror in configure.ac and rerun ./autogen.sh

 3) Apply this patch to /usr/lib/glib-2.0/glibconfig.h:

diff -ur glib-2.2.1/configure.in glib-2.2.1-deb/configure.in
--- glib-2.2.1/configure.in     2003-01-28 14:00:02.000000000 -0800
+++ glib-2.2.1-deb/configure.in 2003-05-29 11:52:10.000000000 -0700
@@ -1969,9 +1969,9 @@
 #define G_MAXLONG      $glib_Ml
 #define G_MAXULONG     $glib_Mul

-#define G_MININT64     ((gint64)  0x8000000000000000)
-#define G_MAXINT64     ((gint64)  0x7fffffffffffffff)
-#define G_MAXUINT64    ((guint64) 0xffffffffffffffff)
+#define G_MININT64     ((gint64)  0x8000000000000000LL)
+#define G_MAXINT64     ((gint64)  0x7fffffffffffffffLL)
+#define G_MAXUINT64    ((guint64) 0xffffffffffffffffLL)

 _______EOF
Comment 1 David Schleef 2003-05-29 20:58:29 UTC 
*** Bug 113993 has been marked as a duplicate of this bug. ***
Comment 2 David Schleef 2003-05-30 02:15:24 UTC 
*** Bug 114002 has been marked as a duplicate of this bug. ***
Comment 3 Benjamin Otte (Company) 2003-05-30 13:00:15 UTC 
Shouldn't this be a glib bug?
Or at least depend on a glib bug?
Comment 4 David Schleef 2003-05-30 19:37:09 UTC 
#108699 is the glib bug.

By the way, the patch above applies to configure.in, not glibconfig.h.
 It can be manually applied to glibconfig.h, though.
Comment 5 David Schleef 2003-06-11 01:46:00 UTC 
There's a new release of Glib, so I think this can be closed.