| View previous topic :: View next topic |
| Author |
Message |
eponymous
Tux's lil' helper
Joined: 02 Feb 2005
Posts: 141
|
 Posted: Wed Oct 16, 2013 9:42 am Post subject: [solved] cyrus-sasl and libsasl2 - ld issue? |
 |
|
Hi all,
I've just done an emerge --unmerge of cyrus-sasl-2.1.26-r3 and have now tried emerging it again (same version).
However, the emerge always fails because it needs libsasl2.so which is removed (obviously) when the package is un-emerged.
| Code: | | /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lsasl2 |
How can a package depend upon the very library it installs?
If I create a link (manually):
| Code: | | ln -s libsasl2.so.3 libsasl2.so |
then it will work again but I'm not sure if this is correct or not.
Does anyone know the correct way to solve this problem? As I say, I'm not sure if my hack above is correct or will lead to further problems...
Thanks.
Last edited by eponymous on Wed Oct 16, 2013 2:12 pm; edited 1 time in total |
|
| Back to top |
|
 |
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Wed Oct 16, 2013 9:50 am Post subject: |
|
|
 Well, there's that little thing called revdep-rebuild... |
|
| Back to top |
|
|
eponymous
Tux's lil' helper
Joined: 02 Feb 2005
Posts: 141
|
| Posted: Wed Oct 16, 2013 11:13 am Post subject: |
|
|
| VoidMage wrote: | | Well, there's that little thing called revdep-rebuild... |
...except that will do nothing except detect that cyrus-sasl is not installed and hence try and re-emerge it which leads back to the same problem. If you read carefully, I'm implying that cyrus-sasl depends upon itself. |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Wed Oct 16, 2013 12:54 pm Post subject: |
|
|
| Well, a single line from a build log tends to be ambiguous, but if you're sure about it, it's most likely (as no real info was provided) a parallel make problem. |
|
| Back to top |
|
|
eponymous
Tux's lil' helper
Joined: 02 Feb 2005
Posts: 141
|
| Posted: Wed Oct 16, 2013 1:56 pm Post subject: |
|
|
| VoidMage wrote: | | Well, a single line from a build log tends to be ambiguous, but if you're sure about it, it's most likely (as no real info was provided) a parallel make problem. |
I created my own overlay in /usr/local/portage for this package which replaced the current version in the main tree which I then removed and went back to the official version.
I simply did an emerge --unmerge of the overlay version, deleted those files and tried to re-emerge the latest version in the tree.
Could this have caused the issue?
(I didn't want to post massive long build logs as I had already scanned through it and inferred the most appropriate messages)
Also, I've tried MAKEOPTS="-j2" instead of "-j5" without success. |
|
| Back to top |
|
|
eponymous
Tux's lil' helper
Joined: 02 Feb 2005
Posts: 141
|
| Posted: Wed Oct 16, 2013 2:15 pm Post subject: |
|
|
Solved this.
It seems there were some left-over files in /usr/lib64 (libsasl2.so.3.0.0 and libsasl2.so.3 -> libsasl2.so.3.0.0) but there was no: libsasl2.so -> libsasl2.so.3.0.0. This must have been confusing the ebuild and/or linker
I deleted all the files matching "*libsasl*" and re-emerged with success. The re-emerge also added all these files back into /usr/lib64/
I'm not sure why these were left behind when I originally removed cyrus-sasl however :S |
|
| Back to top |
|
|
|
Portage & Programming
