Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 1397 - emerge gnome (among others) seems to get confused about where libraries are located.
Summary: emerge gnome (among others) seems to get confused about where libraries are l...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Spider (RETIRED)
URL:
Whiteboard:
Keywords:
: 1493 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-03-29 14:25 UTC by adam morley
Modified: 2003-02-04 19:42 UTC (History)
2 users (show)

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 adam morley 2002-03-29 14:25:06 UTC
so im running an emerge gnome with a custom portage tmp directory (NFS mounted)
and it doesn't seem to be able to understand that libraries are in /usr/lib. 
other software builds fine (emerge system) but emerge mozilla did this once or
twice.  i fixed those with a few carefully crafted symlinks, along with some
that occured during xfree install.  i'm not really sure why it happens, but
somebody recommended submitting this, as gentoo-user was not able to solve the
problem conclusively......

thanks.



/bin/sh ../libtool --mode=link gcc  -mcpu=i686 -march=i686 -O3 -pipe
-fforce-addr -funroll-loops -frerun-cse-after-loop -frerun-loop-opt  -o
libgnomevfs.la -rpath /usr/lib  fnmatch.lo gnome-vfs-application-registry.lo
gnome-vfs-async-ops.lo gnome-vfs-backend.lo gnome-vfs-cancellable-ops.lo
gnome-vfs-cancellation.lo gnome-vfs-configuration.lo gnome-vfs-context.lo
gnome-vfs-directory-filter.lo gnome-vfs-directory.lo gnome-vfs-file-info.lo
gnome-vfs-find-directory.lo gnome-vfs-handle.lo gnome-vfs-i18n.lo
gnome-vfs-inet-connection.lo gnome-vfs-init.lo gnome-vfs-iobuf.lo
gnome-vfs-messages.lo gnome-vfs-method.lo gnome-vfs-mime-handlers.lo
gnome-vfs-mime-info.lo gnome-vfs-mime-magic.lo gnome-vfs-mime-monitor.lo
gnome-vfs-mime-sniff-buffer.lo gnome-vfs-mime.lo
gnome-vfs-module-callback-module-api.lo gnome-vfs-module-callback-private.lo
gnome-vfs-module-callback.lo gnome-vfs-module-shared.lo gnome-vfs-module.lo
gnome-vfs-ops.lo gnome-vfs-parse-ls.lo gnome-vfs-private-utils.lo
gnome-vfs-private.lo gnome-vfs-process.lo gnome-vfs-regexp-filter.lo
gnome-vfs-result.lo gnome-vfs-seekable.lo gnome-vfs-shellpattern-filter.lo
gnome-vfs-socket-buffer.lo gnome-vfs-socket.lo gnome-vfs-ssl.lo
gnome-vfs-transform.lo gnome-vfs-uri.lo gnome-vfs-utils.lo gnome-vfs-xfer.lo
libcharset/libcharset.la								-L/usr/lib -rdynamic -lgmodule -lgthread -lglib
-lpthread -ldl				
	-L/usr/lib -lORBitCosNaming -lORBit -lIIOP -lORBitutil -lglib -lm	
        			-L/usr/lib -loaf -lORBitCosNaming -lORBit -lIIOP -lORBitutil -lglib
-lm					-L/usr/lib -lxml -lz	
        			-rdynamic -L/usr/lib -L/usr/X11R6/lib -lgconf-gtk-1 -lgconf-1 -loaf
-lORBitCosNaming -lORBit -lIIOP -lORBitutil -lgtk -lgdk -lgmodule -lglib -ldl
-lXi -lXext -lX11 -lm 					
-L/usr/lib -lssl -lcrypto -ldl 				 -lrt 
libtool: link: warning: library `/usr/lib/libORBitCosNaming.la' was moved.
libtool: link: warning: library `/usr/lib/libORBit.la' was moved.
grep: /temp/ptmp/portage/ORBit-0.5.14/image//usr/lib/libORBit.la: No such file
or directory
sed: can't read /temp/ptmp/portage/ORBit-0.5.14/image//usr/lib/libORBit.la: No
such file or directory
libtool: link: `/temp/ptmp/portage/ORBit-0.5.14/image//usr/lib/libORBit.la' is
not a valid libtool archive
make[3]: *** [libgnomevfs.la] Error 1
make[3]: Leaving directory
`/temp/ptmp/portage/gnome-vfs-1.0.5/work/gnome-vfs-1.0.5/libgnomevfs'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/temp/ptmp/portage/gnome-vfs-1.0.5/work/gnome-vfs-1.0.5/libgnomevfs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/temp/ptmp/portage/gnome-vfs-1.0.5/work/gnome-vfs-1.0.5'
make: *** [all-recursive-am] Error 2
make  all-recursive
make[1]: Entering directory
`/temp/ptmp/portage/gnome-vfs-1.0.5/work/gnome-vfs-1.0.5'
Making all in libgnomevfs
make[2]: Entering directory
`/temp/ptmp/portage/gnome-vfs-1.0.5/work/gnome-vfs-1.0.5/libgnomevfs'
Making all in libcharset
make[3]: Entering directory
`/temp/ptmp/portage/gnome-vfs-1.0.5/work/gnome-vfs-1.0.5/libgnomevfs/libcharset'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory
`/temp/ptmp/portage/gnome-vfs-1.0.5/work/gnome-vfs-1.0.5/libgnomevfs/libcharset'
make[3]: Entering directory
`/temp/ptmp/portage/gnome-vfs-1.0.5/work/gnome-vfs-1.0.5/libgnomevfs'
/bin/sh ../libtool --mode=link gcc  -mcpu=i686 -march=i686 -O3 -pipe
-fforce-addr -funroll-loops -frerun-cse-after-loop -frerun-loop-opt  -o
libgnomevfs.la -rpath /usr/lib  fnmatch.lo gnome-vfs-application-registry.lo
gnome-vfs-async-ops.lo gnome-vfs-backend.lo gnome-vfs-cancellable-ops.lo
gnome-vfs-cancellation.lo gnome-vfs-configuration.lo gnome-vfs-context.lo
gnome-vfs-directory-filter.lo gnome-vfs-directory.lo gnome-vfs-file-info.lo
gnome-vfs-find-directory.lo gnome-vfs-handle.lo gnome-vfs-i18n.lo
gnome-vfs-inet-connection.lo gnome-vfs-init.lo gnome-vfs-iobuf.lo
gnome-vfs-messages.lo gnome-vfs-method.lo gnome-vfs-mime-handlers.lo
gnome-vfs-mime-info.lo gnome-vfs-mime-magic.lo gnome-vfs-mime-monitor.lo
gnome-vfs-mime-sniff-buffer.lo gnome-vfs-mime.lo
gnome-vfs-module-callback-module-api.lo gnome-vfs-module-callback-private.lo
gnome-vfs-module-callback.lo gnome-vfs-module-shared.lo gnome-vfs-module.lo
gnome-vfs-ops.lo gnome-vfs-parse-ls.lo gnome-vfs-private-utils.lo
gnome-vfs-private.lo gnome-vfs-process.lo gnome-vfs-regexp-filter.lo
gnome-vfs-result.lo gnome-vfs-seekable.lo gnome-vfs-shellpattern-filter.lo
gnome-vfs-socket-buffer.lo gnome-vfs-socket.lo gnome-vfs-ssl.lo
gnome-vfs-transform.lo gnome-vfs-uri.lo gnome-vfs-utils.lo gnome-vfs-xfer.lo
libcharset/libcharset.la								-L/usr/lib -rdynamic -lgmodule -lgthread -lglib
-lpthread -ldl				
	-L/usr/lib -lORBitCosNaming -lORBit -lIIOP -lORBitutil -lglib -lm	
        			-L/usr/lib -loaf -lORBitCosNaming -lORBit -lIIOP -lORBitutil -lglib
-lm					-L/usr/lib -lxml -lz	
        			-rdynamic -L/usr/lib -L/usr/X11R6/lib -lgconf-gtk-1 -lgconf-1 -loaf
-lORBitCosNaming -lORBit -lIIOP -lORBitutil -lgtk -lgdk -lgmodule -lglib -ldl
-lXi -lXext -lX11 -lm 					
-L/usr/lib -lssl -lcrypto -ldl 				 -lrt 
libtool: link: warning: library `/usr/lib/libORBitCosNaming.la' was moved.
libtool: link: warning: library `/usr/lib/libORBit.la' was moved.
grep: /temp/ptmp/portage/ORBit-0.5.14/image//usr/lib/libORBit.la: No such file
or directory
sed: can't read /temp/ptmp/portage/ORBit-0.5.14/image//usr/lib/libORBit.la: No
such file or directory
libtool: link: `/temp/ptmp/portage/ORBit-0.5.14/image//usr/lib/libORBit.la' is
not a valid libtool archive
make[3]: *** [libgnomevfs.la] Error 1
make[3]: Leaving directory
`/temp/ptmp/portage/gnome-vfs-1.0.5/work/gnome-vfs-1.0.5/libgnomevfs'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/temp/ptmp/portage/gnome-vfs-1.0.5/work/gnome-vfs-1.0.5/libgnomevfs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/temp/ptmp/portage/gnome-vfs-1.0.5/work/gnome-vfs-1.0.5'
make: *** [all-recursive-am] Error 2

!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 16, Exitcode 2
!!! (no error message)

!!! emerge aborting on  /usr/portage/gnome-base/gnome-vfs/gnome-vfs-1.0.5.ebuild
Comment 1 Spider (RETIRED) gentoo-dev 2002-04-01 01:01:37 UTC
this -may- be a libtool bug, or am I wrong here?
1 fix is to make gnome-vfs use "make" instead of "emake" 

Not sure about other fixes, gnome-vfs may need libtool --copy --force?


Comment 2 Martin Schlemmer (RETIRED) gentoo-dev 2002-04-01 14:42:06 UTC
It will be ORBit with the libtool issue ...

What version of ORBit do you have installed ?
Comment 3 adam morley 2002-04-01 21:35:23 UTC
well, i have since "upgraded" to version 1.0 of gentoo.  now im compiling xfree,
but getting similar symptoms (as i did before)

this was just after emerge system finished.....


make[3]: Leaving directory `/var/tmp/portage/xfree-4.2.0-r8/work/xc/lib/GLw'
including in lib/dps...
make[3]: Entering directory `/var/tmp/portage/xfree-4.2.0-r8/work/xc/lib/dps'
checking ../../config/pswrap/pswrap over in ../../config/pswrap first...
make[4]: Entering directory
`/var/tmp/portage/xfree-4.2.0-r8/work/xc/config/pswrap'
gcc -O2 -mcpu=i686 -pipe -ansi     -I../.. -I../../exports/include   -Dlinux
-D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE
-D_BSD_SOURCE -D_SVID_SOURCE  -D_GNU_SOURCE   -DFUNCPROTO=15 -DNARROWPROTO  
-DXENVIRONMENT    -c -o main.o main.c
bison -y -d pswparser.y
conflicts:  1 shift/reduce
bison: cannot open file
`/var/tmp/portage/bison-1.34/image//usr/share/bison/bison.simple': No such file
or directory
make[4]: *** [pswparser.c] Error 2
make[4]: Leaving directory
`/var/tmp/portage/xfree-4.2.0-r8/work/xc/config/pswrap'
make[3]: *** [../../config/pswrap/pswrap] Error 2
make[3]: Leaving directory `/var/tmp/portage/xfree-4.2.0-r8/work/xc/lib/dps'
make[2]: *** [includes] Error 2
make[2]: Leaving directory `/var/tmp/portage/xfree-4.2.0-r8/work/xc/lib'
make[1]: *** [includes] Error 2
make[1]: Leaving directory `/var/tmp/portage/xfree-4.2.0-r8/work/xc'
make: *** [World] Error 2

!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 2, Exitcode 2
!!! (no error message)

!!! emerge aborting on  /usr/portage/x11-base/xfree/xfree-4.2.0-r8.ebuild .
Comment 4 Martin Schlemmer (RETIRED) gentoo-dev 2002-04-02 14:32:30 UTC
Hi.

Try the following and let me know:

# emerge --clean rsync
# emerge bison

This should give you bison-1.34-r1.  Then merge xfree again.
Comment 5 adam morley 2002-04-03 00:28:10 UTC
Gah!  that worked! and the portage tree was new as of sunday!  why did it
work!?  grr.  does this mean ill need to do it each time i run into a problem
like this?
Comment 6 Spider (RETIRED) gentoo-dev 2002-04-04 00:01:24 UTC
*** Bug 1493 has been marked as a duplicate of this bug. ***
Comment 7 Spider (RETIRED) gentoo-dev 2002-04-04 00:06:07 UTC
libtoolize of gnome-vfs should fix this problem, commited. 

reopen this bug if things still go wrong (I'm still unable to verify that this
was really the error)
Comment 8 adam morley 2002-04-04 00:23:13 UTC
i actually submitted a new bug, b/c i got the same kind of error when compiling
vim.

bug 1518.  i have yet to "get" to gnome-vfs.....so i can't tell you if its still
there.  i do need to do an emerge --clean rsync, correct?