public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Claudio Bley" <bley@cs.uni-magdeburg.de>
To: Jeff Holle <jeff.holle@verizon.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Problems with gcc 3.2
Date: Wed, 23 Oct 2002 03:31:00 -0000	[thread overview]
Message-ID: <15798.31399.247169.413219@wh2-19.st.uni-magdeburg.de> (raw)
In-Reply-To: <3DB772E2.2040602@verizon.net>

>>>>> "Jeff" == Jeff Holle <jeff.holle@verizon.net> writes:
    Jeff>      $python hello.py Traceback (most recent call last):
    Jeff> File "hello.py", line 1, in ?  import HELLO ImportError:
    Jeff> libstdc++.so.5: cannot open shared object file: No such file
    Jeff> or directory

    Jeff> This appears to be because libstdc++.so.5 is installed in
    Jeff> /usr/local/lib instead of /usr/lib (where the 2.96.0 shared
    Jeff> libraries seem to be).

    Jeff> What do I have to do to my environment to fix this?

    Jeff> Note: I tried to define LD_LIBRARY_PATH (which was not
    Jeff> previously defined) to "/usr/local/lib:/usr/lib:/lib", to no
    Jeff> affect.

Did you export that variable? It should work then. (and you don't need
to specify paths already searched for, just /usr/local/lib)

On the other hand you might just add /usr/local/lib to /etc/ld.so.conf
and run ldconfig. Afterwards running ldd on HELLO.so all library
references should be resolved.

-- 
Claudio Bley                                 ASCII ribbon campaign (")
Debian GNU/Linux advocate                     - against HTML email  X 
http://www.cs.uni-magdeburg.de/~bley/                     & vCards / \

  reply	other threads:[~2002-10-23 10:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 21:16 Jeff Holle
2002-10-23  3:31 ` Claudio Bley [this message]
2002-10-23 10:17 ` Ricardo Anguiano
2002-10-23 10:30   ` bjorn rohde jensen
2002-10-23 11:33     ` Ricardo Anguiano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15798.31399.247169.413219@wh2-19.st.uni-magdeburg.de \
    --to=bley@cs.uni-magdeburg.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jeff.holle@verizon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).