[gentoo-amd64] Re: xine-lib failure

[Duncan]

Paul Stear posted on Wed, 23 Dec 2009 13:55:40 +0000 as excerpted:

> I have moved to a ~amd64 setup but am having a few problems resolving
> some failures.
> media-libs/xine-lib-1.1.17 is failing because it can't find libgomp,
> this is the error:
> /bin/sed: can't read /usr/lib/../lib64/libgomp.la: No such file or
> directory libtool: link: `/usr/lib/../lib64/libgomp.la' is not a valid
> libtool archive
>
> slocate finds these:
> /usr/lib64/gcc/x86_64-pc-linux-gnu/4.4.2/32/libgomp.la
> /usr/lib64/gcc/x86_64-pc-linux-gnu/4.4.2/libgomp.la
> /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.4/32/libgomp.la
> /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.4/libgomp.la
>
> Do I just have a link that is wrong, or do I need to change some setup?
> any ideas?

For that one, try merging lafilefixer, then run it with the --justfixit 
parameter.  *.la files are a pain, causing nearly as many problems as 
they solve.  What lafilefixer does is fix la files that link to other la 
files, so they link directly to the so files instead.

You will also probably want to run revdep-rebuild if you haven't yet 
(running lafilefixer first will likely reduce the number of rebuilds you 
need), and after doing an emerge --deep --newuse @world, you'll want to 
do an emerge --ask --depclean, being sure to check for sanity before you 
let it run, then another revdep-rebuild if the depclean removed anything, 
just to be sure.

FWIW, if you don't run these often, you'll likely have quite a list of 
rebuilds.  But if you run them routinely, after every emerge --update --
deep --newuse @world (and yes, I always use deep newuse), it'll be much 
easier and you'll have far less problems as the system will be kept in a 
far cleaner state routinely.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman