Summary: | kdepim-3.3.0-r1 fails compile, kalarm, libstdc++ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | vordhosbn <vordhosbn> |
Component: | [OLD] KDE | Assignee: | Please assign to toolchain <gcc-porting> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | groepaz |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
vordhosbn
2004-09-24 21:03:23 UTC
DO_NOT_COMPILE="kalarm" emerge -v kdepim does function as a work around for this problem, fyi. of course this is not a fix; having the use of kalarm is optimal. It seems that some of your libraries are compiled with previous versions of gcc. Can you try to emerge arts again? i have a simelar problem on ppc (arch should be changed to "all") ... compiling kalarm fails with g++ -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../kalarm -I../kalarm/widgets -I../libical/src -I../libkdepim -I../libkdenetwork -I/usr/kde/3.3/include -I/usr/qt/3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -D_FILE_OFFSET_BITS=64 -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -O2 -mcpu=7400 -maltivec -mabi=altivec -pipe -mpowerpc-gfxopt -fsigned-char -mstring -mmultiple -fomit-frame-pointer -fno-strict-aliasing -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o alarmguiiface_skel.o `test -f 'alarmguiiface_skel.cpp' || echo './'`alarmguiiface_skel.cpp /bin/sh ../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -O2 -mcpu=7400 -maltivec -mabi=altivec -pipe -mpowerpc-gfxopt -fsigned-char -mstring -mmultiple -fomit-frame-pointer -fno-strict-aliasing -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -o kalarm -L/usr/X11R6/lib -L/usr/qt/3/lib -L/usr/kde/3.3/lib -R /usr/kde/3.3/lib -R /usr/qt/3/lib -R /usr/X11R6/lib birthdaydlg.o alarmevent.o editdlg.o alarmcalendar.o soundpicker.o daemon.o daemongui.o main.o kalarmapp.o mainwindowbase.o mainwindow.o messagewin.o preferences.o prefdlg.o traywindow.o dcophandler.o recurrenceedit.o deferdlg.o functions.o fontcolour.o fontcolourbutton.o alarmtimewidget.o specialactions.o datetime.o reminder.o synchtimer.o eventlistviewbase.o alarmlistview.o kamail.o timeselector.o templatelistview.o templatepickdlg.o templatedlg.o alarmguiiface_skel.o ../kalarm/widgets/libwidgets.la ../libkcal/libkcal.la ../libkdenetwork/libkdenetwork.la ../kalarmd/libkalarmd.la ../libkdepim/libkdepim.la -lkabc -lkdeui -lartskde /usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.1/../../../../powerpc-unknown-linux-gnu/bin/ld: warning: libstdc++.so.5, needed by /usr/kde/3.3/lib/libkspell.so, may conflict with libstdc++.so.6 /usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.1/../../../../powerpc-unknown-linux-gnu/bin/ld: warning: libstdc++.so.5, needed by /usr/kde/3.3/lib/libkspell.so, may conflict with libstdc++.so.6 /usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.1/../../../../powerpc-unknown-linux-gnu/bin/ld: warning: libstdc++.so.5, needed by /usr/kde/3.3/lib/libkspell.so, may conflict with libstdc++.so.6 /usr/kde/3.3/lib/libartsflow.so: undefined reference to `jack_ringbuffer_read' /usr/kde/3.3/lib/libartsflow.so: undefined reference to `jack_ringbuffer_write_space' /usr/kde/3.3/lib/libartsflow.so: undefined reference to `jack_ringbuffer_read_space' /usr/kde/3.3/lib/libartsflow.so: undefined reference to `jack_ringbuffer_write' /usr/kde/3.3/lib/libartsflow.so: undefined reference to `jack_ringbuffer_create' collect2: ld returned 1 exit status make[3]: *** [kalarm] Error 1 make[3]: Leaving directory `/var/tmp/portage/kdepim-3.3.0-r1/work/kdepim-3.3.0/kalarm' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/kdepim-3.3.0-r1/work/kdepim-3.3.0/kalarm' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/kdepim-3.3.0-r1/work/kdepim-3.3.0' make: *** [all] Error 2 !!! ERROR: kde-base/kdepim-3.3.0-r1 failed. !!! Function kde_src_compile, Line 142, Exitcode 2 !!! died running emake, kde_src_compile:make ...since i want to use kalarm, not compiling it is not quite acceptable for me. i will now emerge alsa again (it might indeed be compiled with an earlier version of gcc) and try again. gcc version bumping appearently needs more testing me thinks :=P ok, so reemerging alsa didnt do the trick... now trying with DO_NOT_COMPILE="kalarm" to see if there is another problem. out of curiousity...i am getting the same problem when i try to emerge the non-stable version of k3b (undefined references to jack....) which makes me suspect it needs some library from the non-stable profile. that works as a workaround for me too..oh well :) i'd still like kalarm so..any hints? You need to re-emerge all of kde so that you're using the same GCC version for all of the libraries. That includes all of its dependencies. mmmh and that means exactly what? "all dependancies" is a bit vague. <rant>and if reemerging everything is a requirement, why doesnt do it automatically?</rant> Did you run revdep-rebuild? I can't help you out here - if you install some kde libraries, then install a newer version of GCC which has broken binary compatibility with older versions, the only recourse you have is to reinstall those base libraries compiled with the latest gcc. You can't mix gcc version compilations. > Did you run revdep-rebuild? no, where does it tell me to do so and why isnt it run automatically when needed? > I can't help you out here - if you install some kde libraries, then install a > newer version of GCC which has broken binary compatibility with older > versions, the only recourse you have is to reinstall those base libraries > compiled with the latest gcc. You can't mix gcc version compilations. i understand that. my point is however that if a new gcc, which potentially breaks binary compatibility of some libraries is bumped to stable profile, the emerge should automatically resolve the issue - ultimativly by forcing everything to be recompiled with the new compiler. (if thats what is really necessary) however in this particular case, all the rest of my system runs with zero problems, even when different parts of eg kde are compiled with different compilers - and i somehow doubt that recompiling the same source with a different compiler would magically fix unresolved references. if someone would just tell me what package contains those symbols/functions that are appearently not found...that would be nice. gcc 3.4.x isn't listed as x86 stable on my portage cache. It looks to me like you need to re-emerge arts and kdelibs, and perhaps some o the multimedia libraries that arts depends on (like jack, for instance). Anyway, this isn't a kde problem as far as I can tell, so I'll let the gcc folks answer any more questions. > gcc 3.4.x isn't listed as x86 stable on my portage cache. eh well...i'm on ppc, guess i should have said that :=P > It looks to me like you need to re-emerge arts and kdelibs, and perhaps some > of the multimedia libraries that arts depends on (like jack, for instance). i honestly still doubt that would fix anything. however the big question still is how i would know about this, and why it doesnt happen automatically. this kind of stuff effectivly defeats automated updates of any sorts and thus isnt really acceptable imho. args....emerging arts and kdelibs appearently isnt all that is needed... :/ however, look #66267 for some further comments mixing gcc versions is bad, dont do it ;) re-build anything still using libstdc++ .so.5 with gcc-3.4 |