public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Korn <dkorn@pixelpower.com>
To: 'Umapathy S' <nsupathy@myrealbox.com>,
	Anthony Lee <al012@energex.com.au>
Cc: gcc-help@gcc.gnu.org
Subject: RE: help :: cant run due to libstdc++
Date: Thu, 01 Mar 2001 07:36:00 -0000	[thread overview]
Message-ID: <718D38CAB6E0D011B2C90060970C28A564271D@EXCHANGESERVER> (raw)

>-----Original Message-----
>From: Umapathy S [ mailto:nsupathy@myrealbox.com ]
>Sent: 01 March 2001 17:13

>I tried to link forcibly as
>    /usr/local/bin/g++ -ohello hello.o 
>-l/usr/local/lib/libstdc++.a.2.10.0
>
>I got the list of errors as follows
>    ld: fatal: library -l/usr/local/lib/libstdc++.a.2.10.0: not found
>(!!!!but it is there and not corrupted)
>    ld: fatal: File processing errors. No output written to hello
>    collect2: ld returned 1 exit status

  Check the file permissions for it: is it not readable by you perhaps?

>>     ld.so.1:hello: fatal: libstdc++.so.2.10.0: open failed: No such
>> file or directory

  This is an error message from the dynamic linker.  Your copy of gcc has
a dynamic link library for libstdc++, and it is not the 'ld' linker that
is failing and complaining, but the 'ld.so' dynamic (run-time) linker.
Note that libstdc++.so.2.10.0 is not the same as libstdc++.a.2.10.0

  Try using

export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/local/lib

to add /usr/local/lib to the places searched by the dynamic linker.

  These are just suggestions: let us know if they work or not.

       DaveK
-- 
 All your base are belong to us!


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

             reply	other threads:[~2001-03-01  7:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01  7:36 David Korn [this message]
2001-03-01 20:39 ` Umapathy S
2001-03-01 20:46   ` Alexandre Oliva
2001-03-01 21:00     ` Umapathy S
2001-03-01 21:54       ` Alexandre Oliva
2001-03-01 21:59       ` Umapathy S
  -- strict thread matches above, loose matches on Subject: below --
2001-02-28 23:25 Umapathy S
2001-02-28 23:32 ` Anthony Lee
2001-03-01  2:38   ` Umapathy S

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=718D38CAB6E0D011B2C90060970C28A564271D@EXCHANGESERVER \
    --to=dkorn@pixelpower.com \
    --cc=al012@energex.com.au \
    --cc=gcc-help@gcc.gnu.org \
    --cc=nsupathy@myrealbox.com \
    /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).