Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 57439 - gnome-vfs won't compile, undefined reference.
Summary: gnome-vfs won't compile, undefined reference.
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: x86 Linux
: High major
Assignee: Gentoo Linux Gnome Desktop Team
URL: http://www.bsdforen.de/archive/index....
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-17 19:54 UTC by Bryan Duff
Modified: 2004-07-19 08:16 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bryan Duff 2004-07-17 19:54:55 UTC
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux-gnu/bin/ld: warning: libssl.so.0.9.6, needed by /usr/lib/liblinc.so, may conflict with libssl.so.0.9.7
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/../../../../i686-pc-linux-gnu/bin/ld: warning: libcrypto.so.0.9.6, needed by /usr/lib/liblinc.so, may conflict with libcrypto.so.0.9.7
../../libgnomevfs/.libs/libgnomevfs-2.so: undefined reference to `bonobo_poa_get_threaded'
collect2: ld returned 1 exit status
make[3]: *** [test-vfolder] Error 1
make[3]: *** Waiting for unfinished jobs....

Reproducible: Always
Steps to Reproduce:
1.emerge gnome-vfs
2. ????
3. profit?

Actual Results:  
Read above.  Details.

Expected Results:  
successful emerge.

Portage 2.0.50-r9 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3_pre20040207-r0,
2.6.7-gentoo-r8)
=================================================================
System uname: 2.6.7-gentoo-r8 i686 AMD Athlon(tm) processor
Gentoo Base System version 1.4.9
distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-tbird -O3 -pipe -fomit-frame-pointer"
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/share/config /usr/lib/mozilla/defaults/pref
/usr/share/config /var/qmail/alias /var/qmail/control /var/vpopmail/domains
/var/vpopmail/etc"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-tbird -O3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo
http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="X aavm alsa apache2 apm arts avi berkdb bonobo cdr crypt cups encode esd
foomaticdb gdbm gif gpm gtk gtk2 gtkhtml guile imap imlib java jpeg kde ldap
libg++ libwww mad maildir mikmod motif mozilla mpeg mysql ncurses nls oggvorbis
opengl oss pam pdflib perl php png postgres python qt quicktime readline sdl
slang spell ssl svga tcltk tcpd truetype x86 xml2 xmms xv zlib"
Comment 1 Spider (RETIRED) gentoo-dev 2004-07-18 05:37:14 UTC
hmm,  Two versions of openssl trying to be linked into the application at once?  bad idea.

Try to simply rebuild "linc"  ( emerge --oneshot linc ) And then retry with gnome-vfs.
Comment 2 Bryan Duff 2004-07-18 11:16:48 UTC
Well remerging linc solved the 'may conflict' errors, but I still get the unresolved symbol error.

../../libgnomevfs/.libs/libgnomevfs-2.so: undefined reference to `bonobo_poa_get_threaded'
collect2: ld returned 1 exit status

And that reference is mentioned in libbonobo's reference manual.  But it's not in libbonobo.a, libbonobo-print.a, libbonobox.a.  
Comment 3 foser (RETIRED) gentoo-dev 2004-07-19 05:26:48 UTC
how did it come to this ? The failures probably are the result of the same type of action, so I wonder what you did to your system (up/downgrading, using outside packages) ? Or is this really a stable system all the way and has always been that way, these type of problems just don't pop-up on a clean system.
Comment 4 Bryan Duff 2004-07-19 08:16:20 UTC
This happened when I decided to remerge evolution, which I haven't done in a while.  Right now I'm remerging system; in the hope that this is some sort of dependency problem (although I don't see why).  But yeah, while the system is ACCEPT_KEYWORDS="~x86", there haven't been any major instability issues with it (hardware or software [nothing that couldn't be fairly easily fixed]).

Does that answer your question?