|
|
Home » U++ TheIDE » U++ TheIDE: Installation, Compiling and Running of theide » theide do not run under ubuntu 5.10
|
Re: theide do not run under ubuntu 5.10 [message #3336 is a reply to message #3335] |
Sat, 20 May 2006 21:37   |
|
forlano wrote on Sat, 20 May 2006 15:22 | I've removed my "old" fedora2 and installed the new Ubuntu 5.10. Then I downloaded u++ 605 but theide do not run (unzipped in /home/vega ) . The message was
./theide: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
|
Try to make symbolic link to libstdc++/so which name is libstcc++.so.5
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: theide do not run under ubuntu 5.10 [message #3363 is a reply to message #3361] |
Sun, 21 May 2006 22:30   |
 |
mirek
Messages: 14255 Registered: November 2005
|
Ultimate Member |
|
|
guido wrote on Sun, 21 May 2006 16:00 |
luzr wrote on Sun, 21 May 2006 18:49 |
guido wrote on Sun, 21 May 2006 12:40 | Sorry, don't know what you mean with your reference to xft and X11.
Wether linking to libstdc++.so or libstc++.a has no bearing on xft or any other X11 library, as all of them are plain C.
Guido
|
Well, I am not quite sure whether I was not doing something bad, however last time I have tried, .so issue was "all or nothing" - either every external libraries had to be linked shared or static, mixing impossible...
Mirek
|
That might be a problem or limitation of the upp build system.
Technically you can pretty much do any mix of shared and static libs thinkable.
Guido
|
Well, maybe it is the time to check again (But if I remember well, at the time I have removed all limitations of upp build system in this area).
However, while I am not quite experienced in linux linking, I am a little bit afraid about what happens when you mix say glibc.a.2 malloc (e.g. in X11 lib) with glibc.so.3 malloc in Xft ?
Mirek
|
|
|
|
|
Re: theide do not run under ubuntu 5.10 [message #3377 is a reply to message #3365] |
Mon, 22 May 2006 14:58   |
guido
Messages: 169 Registered: April 2006
|
Experienced Member |
|
|
luzr wrote on Sun, 21 May 2006 23:11 |
guido wrote on Sun, 21 May 2006 17:05 |
Why do you think that has anything to to with glibc?
Guido
|
Because stdlibc++ has to use glibc (new -> malloc etc..). I am not sure what will happen if I link static stdlibc++ v.5 with shared glibc v.6.
Moreover, there even is no swictch in GCC to do so - you can link with either static or dynamic standard library - and that covers both stdlibc++ and glibc.
Disclaimer: I really do know only a little about these affairs...
Means, please come on and start explaining 
Mirek
|
-Wl,-Bstatic -lstdc++ -> links against libstdc++.a
-Wl,-Bdynamic -lstdc++
This way you can switch between static and shared libs on a case by case basis. Note, that this linker option would be used for all libs that follow, so don't forget to switch back with -Wl,-Bdynamic
That glibc and libstdc++ are currently at soname 6 is incidental.
It doesn't imply any intrinsic relation. Mix and match at will!
Btw., the LSB 3.1 (Linux Standard Base), specifies libstdc++.so.6 for LSB compliant apps to link against.
|
|
|
|
|
Goto Forum:
Current Time: Sat Apr 26 19:24:35 CEST 2025
Total time taken to generate the page: 0.01353 seconds
|
|
|