You are not logged in.
Pages: 1
Need libppl.so.11, gcc 4.6.3 is encountering this error:
cc1plus: error while loading shared libraries: libppl.so.11: cannot open shared object file: No such file or directory
Last edited by padremayi (2012-07-14 21:23:07)
Offline
The latest cc1plus is built against libppl.so.12.
So bottomline, upgrade your system and try again.
Burninate!
Offline
The latest cc1plus is built against libppl.so.12.
So bottomline, upgrade your system and try again.
Thanks for reply.
I'm trying to use old gcc version because 4.7.1 fails on narrowing error.
With 4.7.1 I must use NOWERROR=1 option for skip the errors.
With gcc 4.6.3 I receiving libppl.so.11 error.
Is there a way to solve it?
Last edited by padremayi (2012-07-14 21:32:18)
Offline
I don't know if this is an aweful decision but as a temporary measure I copied libppl.so.12 as libppl.so.11 with
sudo cp /usr/lib/libppl.so.12 /usr/lib/libppl.so.11 I needed that library for sage-math (creating a sandbox to be precise) and it worked just fine.
Offline
Ahahahah. Well, it bought me the time I needed.
Anymore ideas before the problem catches up?
Offline
I don't know if this is an aweful decision but as a temporary measure I copied libppl.so.12 as libppl.so.11 with
sudo cp /usr/lib/libppl.so.12 /usr/lib/libppl.so.11I needed that library for sage-math (creating a sandbox to be precise) and it worked just fine.
-_-
Last edited by padremayi (2012-07-14 21:23:36)
Offline
No, don't. As falconindy already said, that's a bad decision.
Creating a copy and renaming it, doesn't seem any better than creating a symlink to the library, which is also a bad idea.
Offline
Creating a copy and renaming it, doesn't seem any better than creating a symlink to the library, which is also a bad idea.
That was my plan B.
![]()
No seriously, why did libppl.so.11 suddenly disappeared? Isn't it because libppl.so.12 took its place as Gcool suggested it?
Offline
Last edited by padremayi (2012-07-14 21:34:42)
Offline
Last edited by padremayi (2012-07-14 21:24:58)
Offline
Solved? .... The correct way is to rebuild the old gcc against the new ppl.
Offline
Solved? .... The correct way is to rebuild the old gcc against the new ppl.
Last edited by padremayi (2012-07-14 21:25:42)
Offline
Allan wrote:Solved? .... The correct way is to rebuild the old gcc against the new ppl.
It seems that nobody is interested on this problem, GCC 4.7 always fails.
For me it's SOLVED
it seems that you have no clue what you are doing. Allan told you how to solve your "problem": fully update your system then rebuild gcc46.
Offline
padremayi wrote:Allan wrote:Solved? .... The correct way is to rebuild the old gcc against the new ppl.
It seems that nobody is interested on this problem, GCC 4.7 always fails.
For me it's SOLVEDit seems that you have no clue what you are doing. Allan told you how to solve your "problem": fully update your system then rebuild gcc46.
I downgraded gcc, gcc-libs and ppl and after that I upgraded again. Is it not enough?
How about rebuild? I'm a newbie and Linux expert always uses max 30 letters for his answer!
EDIT: here
Last edited by padremayi (2012-07-14 21:26:44)
Offline
you should have your machine fully updated so gcc47 which is linked against ppl 1.0 works properly. to build gcc 4.6.3, you can grab it from AUR https://aur.archlinux.org/packages.php?ID=58748. to build a package, you can check the wiki, look for makepkg to begin with. oh and remove libppl.so.11 from your machine of course.
Offline
you should have your machine fully updated so gcc47 which is linked against ppl 1.0 works properly. to build gcc 4.6.3, you can grab it from AUR https://aur.archlinux.org/packages.php?ID=58748. to build a package, you can check the wiki, look for makepkg to begin with. oh and remove libppl.so.11 from your machine of course.
Try before writing, not so simple :-)
There's a bug but now it works.
Read here
Last edited by padremayi (2012-07-14 21:35:55)
Offline
Pages: 1