Summary: | dev-libs/glib-2.26.1 Build error | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Moonfire <mail> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | pchrist |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
libdbus-1.so.output |
Description
Moonfire
2011-01-13 19:14:41 UTC
Created attachment 259735 [details]
build.log
Seems, there's something wrong with your libdbus-1.0 - those symbols should be there. (In reply to comment #2) > Seems, there's something wrong with your libdbus-1.0 - those symbols should be > there. > I've updated allready all related *dbus* packages and libs, that I can build without glib-2.26.x, but without success. I alos run allready lafilefixer, but whithout sueccess to. glib crashes all time @ /var/tmp/portage/dev-libs/glib-2.26.1/work/glib-2.26.1/gio/tests/gdbus-serialization.c (In reply to comment #3) > (In reply to comment #2) > > Seems, there's something wrong with your libdbus-1.0 - those symbols should be > > there. > > > > I've updated allready all related *dbus* packages and libs, that I can build > without glib-2.26.x, but without success. I alos run allready lafilefixer, but > whithout sueccess to. > > glib crashes all time @ > /var/tmp/portage/dev-libs/glib-2.26.1/work/glib-2.26.1/gio/tests/gdbus-serialization.c > What I found out at internet, that new glib depends on dbus. dbus-glib need glib and new glib needs dbus, so I can't fix this problem myself. I hope, any developer have a look to this bug to fix it. ------- snip ------- moonx moonfire # emerge -av dbus-python These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] dev-libs/glib-2.26.1 [2.24.2] USE="fam static-libs%* -debug -doc (-introspection) (-selinux) -test% -xattr" 0 kB [ebuild U ] dev-libs/dbus-glib-0.92 [0.86] USE="-bash-completion -debug -doc -static-libs% -test" 0 kB [ebuild U ] dev-python/dbus-python-0.83.2 [0.83.1] USE="-doc -examples -test" 0 kB ------ snip end ------- google better. glib 2.26 has dbus interface wrapper (gdbus), but it doesn't use libdbus-1.0. Check your libdbus-1.0.so with 'nm -C -D' - those symbols should be present, if they're not, your lib is broken. We're talking here only about sys-apps/dbus here, not the wrappers. Created attachment 259887 [details]
libdbus-1.so.output
As you can see, there are all arguments included in my lib. dbus works fine and only the package within glib can't be build, so it crashes any time.
To use google better is not constructive and wont help anyone.
libdbus-1.so and libdbus-1.0.so exist.
> What I found out at internet, that new glib depends on dbus
And that's not true. As already said, only a few tests depend on libdbus.
Are you sure you don't have more than one copy of libdbus on the system ?
Does i.e. 'scanelf -lq -s dbus_free' mention libdbus ?
(it will print all the libraries using that symbol, not just the one containing it)
(In reply to comment #7) > > What I found out at internet, that new glib depends on dbus > And that's not true. As already said, only a few tests depend on libdbus. > > Are you sure you don't have more than one copy of libdbus on the system ? > > Does i.e. 'scanelf -lq -s dbus_free' mention libdbus ? > (it will print all the libraries using that symbol, not just the one containing > it) > That's my output: scanelf -lq -s dbus_free dbus_free /usr/lib64/libeggdbus-1.so.0.0.0 dbus_free /usr/lib64/libpulsecommon-0.9.21.so dbus_free /usr/lib64/libdbus-1.so.3.5.3 dbus_free /usr/lib64/libdbus-glib-1.so.2.1.0 dbus_free /usr/lib32/libdbus-1.so.3.4.0 dbus_free /usr/lib32/libdbus-glib-1.so.2.1.0 dbus_free /usr/lib/qt4/libQtDBus.so.4.6.3 dbus_free /usr/lib64/qt4/libQtDBus.so.4.6.3 dbus_free /usr/lib32/qt4/libQtDBus.so.4.5.3 There are two libdubus libs, 3.5.3 and 3.4.0. Why is there an old version and how can I fix it (I gues, only delete it is not okay)? Note, that one of them is lib64 and the other lib32, so again, that's not it. Actually, both the lib is given with a path and compile line seems to give correct includes. Perhaps it's a parallel make problem ? (In reply to comment #9) > Note, that one of them is lib64 and the other lib32, so again, that's not it. > > Actually, both the lib is given with a path and compile line seems to give > correct includes. > > Perhaps it's a parallel make problem ? > I'm not sure what you mean with "parallel make", but I only build one package per time, so emerge can't have problems with two processes at same time. I tested now a lot of things, runs revdep-rebuild, fixed libs but all without success. Sorry, I'm no developer, so for me it looks all time as glib problem. If you have an other idea what I can try, please let me know. (In reply to comment #10) > I'm not sure what you mean with "parallel make" He means, give it a try with MAKEOPTS="-j1" in your make.conf. I resolve this as TEST-REQUEST. Please, reopen if it still fails. The linking command obviously misses "-ldbus-1". The question is: why is it missing? --- the important bit from the attached build.log ---- libtool: link: x86_64-pc-linux-gnu-gcc -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -march=athlon64 -O2 -pipe -msse3 -Wall -Wl,-O1 -o .libs/gdbus-serialization gdbus_serialization-gdbus-serialization.o gdbus_serialization-gdbus-tests.o -Wl,--as-needed ../../glib/.libs/libglib-2.0.so ../../gthread/.libs/libgthread-2.0.so ../../gobject/.libs/libgobject-2.0.so ../../gio/.libs/libgio-2.0.so /var/tmp/portage/dev-libs/glib-2.26.1/work/glib-2.26.1/gobject/.libs/libgobject-2.0.so /var/tmp/portage/dev-libs/glib-2.26.1/work/glib-2.26.1/gthread/.libs/libgthread-2.0.so /var/tmp/portage/dev-libs/glib-2.26.1/work/glib-2.26.1/gmodule/.libs/libgmodule-2.0.so -ldl /var/tmp/portage/dev-libs/glib-2.26.1/work/glib-2.26.1/glib/.libs/libglib-2.0.so -lresolv -lz /usr/lib64/libdbus-glib-1.so /usr/lib64/libgobject-2.0.so -L/usr/lib64 /usr/lib64/libgthread-2.0.so /usr/lib64/libglib-2.0.so -lpthread -lrt -pthread --- snip --- We got success with these steps by Rene: 1.) dbus-glib save: quickpkg dbus-glib 2.) dbus and dbus-glib uninstall: emerge -C --nodeps dbus dbus-glib 3.) new install of glib 4.a) if 3 works: emerge -av dbus dbus-glib b) if 3 doesn't work: emerge -kav dbus "=dbus-glib-0.86" (use "k" to use the binary package we have saved before with step 1) Forum entry for this case: http://forums.gentoo.org/viewtopic-t-870169.html |