You are not logged in.
Pages: 1
Topic closed
After `pacman -Syu`, some applications report "***: error while loading shared libraries: libgmp.so.3: cannot open shared object file: No such file or directory" .
But `pacman -Ss libgmp` cannot find anything.
Sincerely!
e^(π⋅i) + 1 = 0
Offline
The file is in the "gmp" package, but that is not the issue here. It is caused by out of date packages on your system. Change mirror and try updating again.
Of course if the problem packages are not in the repos, you will need to rebuild them yourself.
Offline
sudo ln -s /usr/lib/libgmp.so.10.0.1 /usr/lib/libgmp.so.3
fix it, thanks!
e^(π⋅i) + 1 = 0
Offline
No... that is known to cause breakages. Fix the actual problem using the instructions I gave above.
Offline
I'm having the same problem - my main mirror suddenly showed a huge update yesterday (111 packages) and now I can't start Xmonad because of the missing gmp library. I've got libgmp.so and libgmp.so.10 links in /usr/lib/, but no libgmp.so.3. I've tried updating and reinstalling gmp from 4 different mirrors, but to no avail. Any help would be greatly appreciated, as I'm stuck in console!
Last edited by ilovesocks (2010-04-10 15:14:59)
Offline
I'm having the same problem - my main mirror suddenly showed a huge update yesterday (111 packages) and now I can't start Xmonad because of the missing gmp library. I've got libgmp.so and libgmp.so.10 links in /usr/lib/, but no libgmp.so.3. I've tried updating and reinstalling gmp from 4 different mirrors, but to no avail. Any help would be greatly appreciated, as I'm stuck in console!
xmonad in the repos is built against the newest gmp. If you're not using that version, simply rebuild xmonad.
Offline
Wow, I didn't realize that an executable is created in ~/.xmonad. Thanks very much!
Offline
Don't symlink incorrect versions to libgmp.so.3 -- unless you enjoy having things coredump randomly or produce weird results. I added "gmp4" to aur (gmp 4.3.2) which provides libgmp.so.3. Run `yaourt libgmp.so.3` and you'll see the package, install it, live happily ever after.
Offline
Or.... you could just fix your issues rather than installing that as a needless workaround....
Offline
sudo ln -s /usr/lib/libgmp.so.10.0.1 /usr/lib/libgmp.so.3
fix it, thanks!
Cheers man that fixed my problems coding stuff in SDL.
"The ecological crisis is a moral issue."
Offline
No... that is known to cause breakages. Fix the actual problem using the instructions I gave above.
Yeah but your instructions were useless. Didn't fix anything... I already figured to try what you said before you even mentioned that.
"The ecological crisis is a moral issue."
Offline
Seriously... all mirrors should have the complete package set ages ago so a full system update will fix all official packages. Any affected AUR packages need to be rebuilt by you.
Offline
sudo ln -s /usr/lib/libgmp.so.10.0.1 /usr/lib/libgmp.so.3
fix it, thanks!
[OFF]I think that we need a new rule at the forum, anyone that suggest to symlink a library need to be banned...[/OFF]
Offline
kazuo -- that'd be kinda cool!
Matt
"It is very difficult to educate the educated."
Offline
sorry a bit OT but was wondering..(and maybe this will enlighten others)
would symlinking a library be the correct way of solving this issue if the distro was not arch linux, maybe a distro without a package manager like slackware? or is it always better to reinstall a package alltogether whether from source or * package manager rather than using a a symlink work around to the output of ldd?
thanks
sleepy 1
Last edited by sleepy (2010-04-28 18:06:12)
Offline
No, symlinking libraries with different sonames is never a solution. Their sonames are different for a reason.
The work around (if rebuilding software is out of the question), is to install a copy of the old library. That can also lead to issues (if a package is link to libfoo.so.1 and libbar.sp.0 and libbar links to libfoo.so.0)
Offline
This could have so been easily solved by:
whereis libgmp
Literally, the exact title of the thread
As for symlinking libraries, please, for the love of god, do not do that unless you are held against your will at gunpoint
Last edited by cesura (2010-04-28 23:43:06)
Offline
I'm having the same problem - my main mirror suddenly showed a huge update yesterday (111 packages) and now I can't start Xmonad because of the missing gmp library. I've got libgmp.so and libgmp.so.10 links in /usr/lib/, but no libgmp.so.3. I've tried updating and reinstalling gmp from 4 different mirrors, but to no avail. Any help would be greatly appreciated, as I'm stuck in console!
Simply doing a
$ xmonad --recompile
fixed my xmonad for me.
Last edited by smoak (2010-04-29 00:13:40)
Offline
See http://bbs.archlinux.org/viewtopic.php?id=90009. Entry #1!
Rules:
Every post must be one of the top 100 sentences appearing in a forum or mailing list reply thread.Don't symlink libraries of different so versions.
Offline
whoops, didnt see that he symlinked a different library -________-. I thought the program was searching for the .so file in the wrong directory and he symlinked the CORRECT .so file to the directory it was looking in
:lol::lol::lol::lol::lol::lol::lol::lol:
ty
Offline
Hi, I'm quite beginner so sorry if the answer to my question is obvious. My situation is the following:
I've installed gmp-5.0.1 in /usr/local without any errors nor warnings. Then I was trying to install mpfr in /usr/local:
$ ./configure - I get ...
...
checking if gmp.h version and libgmp version are the same... no
configure: WARNING: 'gmp.h' and 'libgmp' seems to have different versions or
configure: WARNING: we cannot run a program linked with GMP (if you cannot
configure: WARNING: see the version numbers above). A cause may be different
configure: WARNING: GMP versions with different ABI's.
configure: WARNING: However since we can't use 'libtool' inside the configure,
configure: WARNING: we can't be sure. See 'config.log' for details.
so I've tried
$./configure --with-gmp=/usr/local - works OK
then $make without any problems and then while
$ make check
I get the error from the first post: error while loading shared libraries: libgmp.so.10: cannot open shared object file: No such file or directory
I've tried to manage it by
- $ export LD_LIBRARY_PATH=/usr/local or (/usr/local/lib) and start from ./configure - nothing
- putting different paths into --with-gmp= - nothing
- combining it with installation of gmp (on the other machine) in different directions
and I still get the same error...
I'd like to add that:
$ locate libgmp.so
/usr/lib/libgmp.so.3
/usr/lib/libgmp.so.3.5.2
/usr/lib/ssl/engines/libgmp.so
/usr/local/gmp-5.0.2/.libs/libgmp.so
/usr/local/gmp-5.0.2/.libs/libgmp.so.10
/usr/local/gmp-5.0.2/.libs/libgmp.so.10.0.2
/usr/local/lib/libgmp.so
/usr/local/lib/libgmp.so.10
/usr/local/lib/libgmp.so.10.0.2
What am I doing wrong? Can anyone help me somehow, please?
No, symlinking libraries with different sonames is never a solution.
and what about linking in my situation?
Thank you very much in advance.
Last edited by ramanujan (2011-05-24 04:17:07)
Offline
Hi, I'm quite beginner so sorry if the answer to my question is obvious. My situation is the following:
I've installed gmp-5.0.1 in /usr/local without any errors nor warnings. Then I was trying to install mpfr in /usr/local:
$ ./configure - I get ...
...
checking if gmp.h version and libgmp version are the same... no
configure: WARNING: 'gmp.h' and 'libgmp' seems to have different versions or
configure: WARNING: we cannot run a program linked with GMP (if you cannot
configure: WARNING: see the version numbers above). A cause may be different
configure: WARNING: GMP versions with different ABI's.
configure: WARNING: However since we can't use 'libtool' inside the configure,
configure: WARNING: we can't be sure. See 'config.log' for details.so I've tried
$./configure --with-gmp=/usr/local - works OK
then $make without any problems and then while
$ make check
I get the error from the first post: error while loading shared libraries: libgmp.so.10: cannot open shared object file: No such file or directoryI've tried to manage it by
- $ export LD_LIBRARY_PATH=/usr/local or (/usr/local/lib) and start from ./configure - nothing
- putting different paths into --with-gmp= - nothing
- combining it with installation of gmp (on the other machine) in different directionsand I still get the same error...
I'd like to add that:
$ locate libgmp.so
/usr/lib/libgmp.so.3
/usr/lib/libgmp.so.3.5.2
/usr/lib/ssl/engines/libgmp.so
/usr/local/gmp-5.0.2/.libs/libgmp.so
/usr/local/gmp-5.0.2/.libs/libgmp.so.10
/usr/local/gmp-5.0.2/.libs/libgmp.so.10.0.2
/usr/local/lib/libgmp.so
/usr/local/lib/libgmp.so.10
/usr/local/lib/libgmp.so.10.0.2What am I doing wrong? Can anyone help me somehow, please?
Allan wrote:No, symlinking libraries with different sonames is never a solution.
and what about linking in my situation?
Thank you very much in advance.
May I ask why are you compiling the apps yourself rather than installing them via pacman?
Do you rally need gmp 5.0.1 (we have a newer version in the repos now)? You can download it from http://arm.konnichi.com/search/index.ph … ommunity=1
Last edited by karol (2011-05-24 04:56:51)
Offline
Bumping an ancient thread because it looks like there's a thousand symlinked libraries in /usr/lib now, and I was curious if someone could educate me on the philosophy change.
Offline
Dont't necrobump. For no reason. Never.
Symlinking minor releases to major releases is normal, ie. foo.so linking to foo.so.1 linking to foo.so.1.2 - what's discouraged (because it's a really bad idea) is to link eg. foo.so.1.2 to foo.so.1.3 (the approach in post #3)
Offline
Please do not necrobump.
Closing.
Offline
Pages: 1
Topic closed