Bugzilla Bug 9583

this is a problem i'm having with aspell that i believe i've traced to libtool.
if this is not a problem with libtool, please change this accordingly.


i do the following:
1. mask aspell-0.50.2 in package.mask
2. emerge aspell    /* 0.50.1 is installed */
3. unmask aspell-0.50.2 in package mask
4. emerge -u aspell /* installs 0.50.2 */
5. at this point, ldd /usr/lib/libaspell.so shows the following:

libaspell-common-0.50.1.so => /usr/lib/libaspell-common-0.50.1.so
(0x6ff0a000) /* !!! this is the libaspell-common from 0.50.1 !!! */
...

6. if i then emerge clean, and ldd /usr/lib/libaspell.so, i get:
libaspell-common-0.50.1.so => not found
...

7. if i completely remove aspell from my system and then emerge version
0.50.2, ldd /usr/lib/libaspell.so yields:

libaspell-common-0.50.2.so => /usr/lib/libaspell-common-0.50.2.so
(0x6ff0a000)  /* this is the libaspell-common from 0.50.2 */
...


the problem occurs during the emerge when the temporary image is
created. this step causes libaspell.so to get relinked, but this time
with -L/usr/lib and -laspell-common. and since there _is_ a
libaspell-common.so present (the 0.50.1 version) when i'm upgrading, the
relink causes libaspell.so from 0.50.2 to link against
libaspell-common.so from 0.50.1. i think this is a bug.

nall, what happens if you FEATURES="-sandbox" and do all these things?

I will try that myself, but good to get a second hand with it.  Also, with that
try turning off the elibtoolize statement in the ebuild...

this is being observed on a PPC, so FEATURES="-sandbox" is already in effect. 

i also tried it on my x86 box and observed identical behavior. 

i did try commenting out the elibtoolize statement, but the behavior persists.

On Wed, 2002-10-23 at 05:02, nall wrote:

> the problem occurs during the emerge when the temporary image is
> created. this step causes libaspell.so to get relinked, but this time
> with -L/usr/lib and -laspell-common. and since there _is_ a
> libaspell-common.so present (the 0.50.1 version) when i'm upgrading, the
> relink causes libaspell.so from 0.50.2 to link against
> libaspell-common.so from 0.50.1. i think this is a bug.
> 

Yes, it is.

> i hope this isn't too confusing. i just wanted to run it by you before
> filing it in case it was a known issue or a non-bug.
> 

I first heard of it when we had issues with nautilus2 when nautilus1 was
already installed.

Check /usr/portage/eclass/libtool.eclass, the "reversedeps" patch.  Try
to change in both ebuilds the elibtoolize line from:

  elibtoolize

to:

  elibtoolize --reverse-deps

And see if that fixes it.

More info on the nautilus issue can be found at:

  http://bugzilla.gnome.org/show_bug.cgi?id=75635

confirmed. adding --reverse-deps to the elibtoolize fixes this bug. it probably
ought to be added to the  aspell-0.50.1.ebuild as well, though i haven't checked
to see if it's a problem there.

thanks nall and Az :)