[Python-bugs-list] [ python-Bugs-635929 ] 2.2.2 build on Solaris

noreply@sourceforge.net noreply@sourceforge.net
Thu, 14 Nov 2002 15:23:48 -0800

Bugs item #635929, was opened at 2002-11-09 09:40
You can respond by visiting: 

Category: Build
Group: Platform-specific
Status: Open
Resolution: None
Priority: 5
Submitted By: Guido van Rossum (gvanrossum)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.2.2 build on Solaris

Initial Comment:
Attached is a message that concludes an exchange
between David LeVine and me. He built Python using the
gcc 3.2 from sunfreeware.com.

Running ./python, he got this error:

ld.so.1: ./python: fatal: libstdc++.so.5: open failed:
No such file or directory

I suggested adding a -R somewhere and he got it to work
by patching configure. Perhaps a real fix can be made
out of this?


>Comment By: Guido van Rossum (gvanrossum)
Date: 2002-11-14 18:23

Logged In: YES 

Feel free to close it then. It seemed obscure to me at best.
Maybe a note can be added to README with the solution?


Comment By: Martin v. L÷wis (loewis)
Date: 2002-11-09 13:02

Logged In: YES 

I'm not sure that this should be fixed in Python, there are
several complications:

1. It is not certain that python is linked with libstdc++.
If not, you 
    only need to worry about libgcc_s.so, if gcc is gcc 3.2.

2. It is not certain whether /usr/local is the right prefix; 
    gcc might be installed with a different prefix.

3. It is not certain whether libstdc++ is installed in
<gccprefix>/lib, gcc also supports installing it into

4. Randomly adding -R options might shoot back, since python
may now pick up the wrong libraries, for libraries used in
extension modules.

We usually fix this in the gcc installation, not in all
affected applications, by adding proper -R options into the
installed specs file.

I would rather "fix" this by pointing out that gcc 3 users
will have to set LD_RUN_PATH on Solaris, to include the
directories containing libgcc_s.so.1, and possibly


You can respond by visiting: