50701 2004-05-10 21:43 0000 app-i18n/im-ja-1.1 emerge failed with gtk+-2.4.0-r1 with USE=debug 2004-07-03 19:45:11 0000 1 1 1 Unclassified Gentoo Linux Applications unspecified All Linux RESOLVED FIXED P2 minor --- 1 2tcso6e02@sneakemail.com cjk@gentoo.org 2tcso6e02@sneakemail.com 2004-05-10 21:43:31 0000 I have what appears to be the same bug as #45246: my latest emerge world brought in gtk+-2.4.0-r1, and now im-ja-1.0-r2 won't emerge. The error is: gcc -g -O2 -fstack-protector -g -g -g -o im-ja-conf im_ja_conf-im-ja-conf.o im_ja_conf-conf.o im_ja_conf-error.o im_ja_conf-about-box.o -Wl,--export-dynamic -pthread -Wl,--export-dynamic -Wl,--export-dynamic /usr/lib/libgconf-2.so /usr/lib/libORBit-2.so /usr/lib/libpopt.so /usr/lib/libgthread-2.0.so /usr/lib/libglade-2.0.so /usr/lib/libgtk-x11-2.0.so /usr/lib/libxml2.so -lpthread -lz /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so -lm /usr/lib/libpangoxft-1.0.so /usr/lib/libpangox-1.0.so /usr/lib/libpango-1.0.so /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libglib-2.0.so /usr/lib/libwnn.so -lcrypt -lRKC im_ja_conf-im-ja-conf.o(.text+0x2044): In function `create_dialog': /var/tmp/portage/im-ja-1.0-r2/work/im-ja-1.0/src/im-ja-conf/im-ja-conf.c:674: undefined reference to `GTK_OPTION_MENU' im_ja_conf-im-ja-conf.o(.text+0x2071):/var/tmp/portage/im-ja-1.0-r2/work/im-ja-1.0/src/im-ja-conf/im-ja-conf.c:675: undefined reference to `GTK_OPTION_MENU' collect2: ld returned 1 exit status Reproducible: Always Steps to Reproduce: 1. emerge -DU world 2. 3. Actual Results: emerge of app-i18n/im-ja-1.0-r2 failed. Expected Results: emerged successfully Portage 2.0.50-r6 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.6-rc2) ================================================================= System uname: 2.6.6-rc2 i686 AMD Athlon(tm) XP 1900+ Gentoo Base System version 1.4.9 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-g -O2 -fstack-protector" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-g -O2 -fstack-protector" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs fixpackages nostrip sandbox userpriv" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo ftp://gentoo.ccccom.com http://gentoo.ccccom.com ftp://gentoo.netnitco.net/pub/mirrors/gentoo/source/ ftp://mirrors.tds.net/gentoo http://mirrors.tds.net/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X Xaw3d aalib apm arts avi berkdb canna cdr cjk crypt cups debug doc dvd encode esd foomaticdb freetype freewnn gdbm gif gnome gpm gtk gtk2 guile imlib java joystick jpeg kde libg++ libwww mad maildir matrox mbox mikmod mozilla mozsvg mpeg mule ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline ruby scanner sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype usb video_cards_matrox x86 xinerama xml2 xmms xv zlib" usata@gentoo.org 2004-05-11 08:11:30 0000 This is because you have debug in USE flag. I removed debug USE flag from 1.0-r2. Thanks for the report. 2tcso6e02@sneakemail.com 2004-05-22 19:41:52 0000 Well, I just tried emerging app-i18n/im-ja-1.0-r2 again; I have the new ebuild (I can see where the debug stuff was commented out), but the emerge failed with the same error. In the emerge output, I see: configure: Debugging: yes USE=-debug emerge im-ja worked, and in that case I see: configure: Debugging: no so it looks like the "debug" flag is still being set (maybe in gnome2.eclass: there's code there that looks like it might be doing that, but I don't understand it well enough to be sure). usata@gentoo.org 2004-05-23 01:56:07 0000 You are right. gnome2.eclass pulls in debug IUSE flag. I changed src_compile() to not use gnome2_src_compile. (Debugging Thanks for the bug report. 2tcso6e02@sneakemail.com 2004-07-03 12:41:46 0000 With im-ja-1.1, I'm getting the same errors: ... configure: Debugging: yes ... gcc -g -O2 -fstack-protector -g -g -g -o im-ja-conf im_ja_conf-im-ja-conf.o im_ja_conf-conf.o im_ja_conf-error.o im_ja_conf-about-box.o -Wl,--export-dynamic -pthread -Wl,--export-dynamic -Wl,--export-dynamic /usr/lib/libgconf-2.so /usr/lib/libORBit-2.so /usr/lib/libpopt.so /usr/lib/libgthread-2.0.so /usr/lib/libglade-2.0.so /usr/lib/libgtk-x11-2.0.so /usr/lib/libxml2.so -lpthread -lz /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so -lm /usr/lib/libpangoxft-1.0.so /usr/lib/libpangox-1.0.so /usr/lib/libpango-1.0.so /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libglib-2.0.so im_ja_conf-im-ja-conf.o(.text+0x2234): In function `create_dialog': /var/tmp/portage/im-ja-1.1/work/im-ja-1.1/src/im-ja-conf/im-ja-conf.c:640: undefined reference to `GTK_OPTION_MENU' im_ja_conf-im-ja-conf.o(.text+0x2261):/var/tmp/portage/im-ja-1.1/work/im-ja-1.1/src/im-ja-conf/im-ja-conf.c:641: undefined reference to `GTK_OPTION_MENU' collect2: ld returned 1 exit status make[3]: *** [im-ja-conf] Error 1 make[3]: Leaving directory `/var/tmp/portage/im-ja-1.1/work/im-ja-1.1/src/im-ja-conf' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/im-ja-1.1/work/im-ja-1.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/im-ja-1.1/work/im-ja-1.1' make: *** [all] Error 2 !!! ERROR: app-i18n/im-ja-1.1 failed. !!! Function gnome2_src_compile, Line 39, Exitcode 2 !!! compile failure For now, I just put the line: app-i18n/im-ja -debug in the file /etc/portage/package.use, which is an okay work around. usata@gentoo.org 2004-07-03 19:45:11 0000 Thanks for the reminder. I disabled that on both 1.1 and 1.2..