Closing.
]]>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)
]]>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
]]>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.
]]>:lol::lol::lol::lol::lol::lol::lol::lol:
ty
]]>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.
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.
]]>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
]]>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)
]]>thanks
sleepy 1
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]
]]>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.
]]>