Gentoo Archives: gentoo-user

From: walt <w41ter@×××××.com>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Re: libjpeg, 6 vs 7, and emacs
Date: Wed, 23 Sep 2009 20:22:30
Message-Id: h9e012$mif$
In Reply to: [gentoo-user] libjpeg, 6 vs 7, and emacs by
1 On 09/23/2009 10:14 AM, felix@×××××××.com wrote:
2 > Gentoo updates refuse to install both versions 6 and 7 of jpeg,
3 > and I have found that certain applications, like emacs, refuse
4 > to remerge with -7 so I have been refusing the -7 update for a
5 > month or two now. Every once in a while, one slips by me,
6 > usually because I forget to remove thunderbird from the list of
7 > updates, and I find out when emacs won't run. If I try to build
8 > emacs with -7, it complains, so I remerge jpeg-6 and then emacs
9 > is happy again. I do not understand the compat lib; it also blocks,
10 > and since I can just refuse the -7 update and keep on working, I
11 > have not looked into it much, figuring that sooner or later emacs
12 > and other packages will be upgraded to handle jpeg-7.
13 >
14 > Recently another jpeg-7 upgrade slipped past me, only this time it
15 > got weird. I remerged jpeg-6 and found that emacs now complained
16 > that jpeg-7 was missing. Here is "ldd /usr/emacs/bin|grep jpeg":
17 >
18 > => /usr/lib/ (0x00007f0cbd19f000)
19 > => not found
20 >
21 > Now I am puzzled. If jpeg-6 and -7 block each other, how did
22 > emacs end up expecting both?...
24 ldd is actually recursive and lists not only the libs linked to
25 emacs directly but also they libs *they* are linked to.
27 There was a bug recently where the same library was both 'found'
28 and 'not found' at the same time.
30 If you do an ldd on each of the libs separately you should find
31 out which one is expecting which libjpeg.
33 BTW, I have jpeg-7 on my ~amd64 machine and I didn't even know it,
34 and emacs works okay. I can see why it wouldn't work for you as
35 long as emacs has conflicting dependencies like the above, though.


Subject Author
Re: [gentoo-user] Re: libjpeg, 6 vs 7, and emacs felix@×××××××.com