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 662109 - [regression] build failure: ./.libs/libgtk-x11-2.0.so: undefined reference to `g_value_get_schar'
[regression] build failure: ./.libs/libgtk-x11-2.0.so: undefined reference t...
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
2.24.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
: 671763 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-10-18 16:30 UTC by David Ronis
Modified: 2018-03-14 06:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Ronis 2011-10-18 16:30:45 UTC
I'm trying to build 2.24.7 as part of my update to gnome-3.2.1.   The build dies with:

make[5]: Entering directory `/home/ronis/Project/notar/GNOME/garnome/platform/gtk+-2.0/work/main.d/gtk+-2.24.7/gtk'
/bin/sh ../libtool  --tag=CC   --mode=link /usr/bin/gcc  -DGDK_PIXBUF_DISABLE_DEPRECATED  -I/opt/garnome-svn-3.2.0/include -L/opt/garnome-svn-3.2.0/lib -O2 -g -pipe -Wall  -Wl,-O1 -L/opt/garnome-svn-3.2.0/lib -o gtk-query-immodules-2.0 queryimmodules.o libgtk-x11-2.0.la ../gdk/libgdk-x11-2.0.la -pthread -L/opt/garnome-svn-3.2.0/lib -lpangocairo-1.0 -lX11 -lXcomposite -lXdamage -lXfixes -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lfreetype -lz -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lm 
libtool: link: /usr/bin/gcc -DGDK_PIXBUF_DISABLE_DEPRECATED -I/opt/garnome-svn-3.2.0/include -O2 -g -pipe -Wall -Wl,-O1 -o .libs/gtk-query-immodules-2.0 queryimmodules.o -pthread  -L/opt/garnome-svn-3.2.0/lib ./.libs/libgtk-x11-2.0.so /home/ronis/Project/notar/GNOME/garnome/platform/gtk+-2.0/work/main.d/gtk+-2.24.7/gdk/.libs/libgdk-x11-2.0.so ../gdk/.libs/libgdk-x11-2.0.so /usr/lib/libXinerama.so /usr/lib/libXi.so /usr/lib/libXrandr.so /usr/lib/libXext.so /usr/lib/libXcursor.so /opt/garnome-svn-3.2.0/lib/libpangocairo-1.0.so /usr/lib/libstdc++.so /usr/lib/libXcomposite.so /usr/lib/libXdamage.so /usr/lib/libXfixes.so /opt/garnome-svn-3.2.0/lib/libatk-1.0.so /opt/garnome-svn-3.2.0/lib/libcairo.so /usr/lib/libpixman-1.so /usr/lib/libXrender.so /usr/lib/libX11.so /usr/lib/libxcb.so /usr/lib/libXau.so /usr/lib/libXdmcp.so /opt/garnome-svn-3.2.0/lib/libgdk_pixbuf-2.0.so /usr/lib/libpng14.so /opt/garnome-svn-3.2.0/lib/libgio-2.0.so -lresolv /opt/garnome-svn-3.2.0/lib/libpangoft2-1.0.so /opt/garnome-svn-3.2.0/lib/libpango-1.0.so /opt/garnome-svn-3.2.0/lib/libfontconfig.so /opt/garnome-svn-3.2.0/lib/libfreetype.so -lz /usr/lib/libexpat.so /opt/garnome-svn-3.2.0/lib/libgobject-2.0.so /usr/lib/libffi.so /opt/garnome-svn-3.2.0/lib/libgmodule-2.0.so -ldl /opt/garnome-svn-3.2.0/lib/libgthread-2.0.so -lpthread /opt/garnome-svn-3.2.0/lib/libglib-2.0.so /opt/garnome-svn-3.2.0/lib/libiconv.so -lrt -lm -pthread -Wl,-rpath -Wl,/opt/garnome-svn-3.2.0/lib
./.libs/libgtk-x11-2.0.so: undefined reference to `g_value_get_schar'
collect2: ld returned 1 exit status
Comment 1 Matthias Clasen 2011-10-21 02:04:22 UTC
Yeah, that is an unfortunate thing that crept into the released tarball.
As a workaround, you can either regenerate the marshallers, or replace
g_value_get_schar by g_value_get_char in the included marshallers. The fedora package has a patch for that.

I'll do another 2.x in a bit, and will make sure that this problem doesn't happen again.
Comment 2 Timothy Arceri 2013-10-17 23:29:52 UTC
*** Bug 671763 has been marked as a duplicate of this bug. ***
Comment 3 David Ronis 2013-10-18 17:46:04 UTC
This no longer happens in gtk+-3.10.2 (and hasn't been happening in many of the earlier versions)
Comment 4 Pacho Ramos 2015-02-18 11:40:55 UTC
Maybe should be fixed too in 2.x for next tarballs
Comment 5 David Heidelberg 2017-09-23 10:32:17 UTC
Would be nice have fixed this issue in 2.x series, because some software still needs it.

At this moment, I noticed that actual Gentoo workaround for this issue is not working right [1].

[1] https://bugs.gentoo.org/629778