public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-amd64] xine-lib failure
@ 2009-12-23 13:55 Paul Stear
  2009-12-23 14:27 ` Paul Stear
  2009-12-23 16:11 ` [gentoo-amd64] " Duncan
  0 siblings, 2 replies; 3+ messages in thread
From: Paul Stear @ 2009-12-23 13:55 UTC (permalink / raw
  To: gentoo-amd64

Hi all,
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?
Paul

-- 
This message has been sent using kmail on gentoo.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-amd64] xine-lib failure
  2009-12-23 13:55 [gentoo-amd64] xine-lib failure Paul Stear
@ 2009-12-23 14:27 ` Paul Stear
  2009-12-23 16:11 ` [gentoo-amd64] " Duncan
  1 sibling, 0 replies; 3+ messages in thread
From: Paul Stear @ 2009-12-23 14:27 UTC (permalink / raw
  To: gentoo-amd64

On Wednesday 23 Dec 2009 13:55:40 Paul Stear wrote:
> Hi all,
> 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?
> Paul
Sorry to reply to my own message.
I suddenly remembered seeing something about justfixit.  Running that solved 
the problem.
Thanks for your time
Compliments of the season
Paul

-- 
This message has been sent using kmail on gentoo.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* [gentoo-amd64]  Re: xine-lib failure
  2009-12-23 13:55 [gentoo-amd64] xine-lib failure Paul Stear
  2009-12-23 14:27 ` Paul Stear
@ 2009-12-23 16:11 ` Duncan
  1 sibling, 0 replies; 3+ messages in thread
From: Duncan @ 2009-12-23 16:11 UTC (permalink / raw
  To: gentoo-amd64

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




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-12-23 18:03 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-23 13:55 [gentoo-amd64] xine-lib failure Paul Stear
2009-12-23 14:27 ` Paul Stear
2009-12-23 16:11 ` [gentoo-amd64] " Duncan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox