From: "Koornstra, Reinoud" <koornstra@hp.com>
To: Ian Lance Taylor <iant@google.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: RE: libstdc issue
Date: Mon, 09 Mar 2009 19:46:00 -0000 [thread overview]
Message-ID: <E92FAF79A8BBC642A36EEE3AA7F152D83CF384C325@GVW1089EXB.americas.hpqcorp.net> (raw)
In-Reply-To: <m3tz669jvp.fsf@google.com>
Hi,
I got around the issue by doing this:
ln -s /usr/lib/libstdc++.so.6.0.10 /lib/libstdc++.so.6
Now swig doesn't have an issue.
How come it's correctly installed in /usr (./configure --prefix=/usr --exec-prefix=/usr) but not while installing it in /lib?
Kind Regards,
Reinoud.
-----Original Message-----
From: Ian Lance Taylor [mailto:iant@google.com]
Sent: Friday, March 06, 2009 5:56 PM
To: Koornstra, Reinoud
Cc: gcc-help@gcc.gnu.org
Subject: Re: libstdc issue
"Koornstra, Reinoud" <koornstra@hp.com> writes:
> I compiled gcc 4.1.2 and installed it.
> Compiled swig as well, however, upon starting it give me this:
>
> swig: /lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /lib/libstdc++.so.6)
>
> These libs come included in gcc and I cannot image that such an inconsistency would exist in the gcc source.
> Any hints how to resolve this?
gcc does not normally install libgcc_s.so.1 in /lib, so my guess is that
that file came from your OS, and your dynamic linker is finding it
before the libgcc_s.so.1 which was installed by gcc. You could try
making it a symlink to the libgcc_s.so.1 which you installed.
Note that you can confuse systems by building and installing gcc into
system directories like /lib, overwriting the system libraries and
compilers. It's often better to install gcc and use it elsewhere.
Ian
prev parent reply other threads:[~2009-03-09 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 22:14 Koornstra, Reinoud
2009-03-07 1:57 ` Ian Lance Taylor
2009-03-07 2:22 ` Koornstra, Reinoud
2009-03-09 19:31 ` which glibc to use Koornstra, Reinoud
2009-03-10 5:47 ` Ian Lance Taylor
2009-03-11 5:03 ` Koornstra, Reinoud
2009-03-11 10:00 ` Kai Ruottu
2009-03-19 19:39 ` gcc options " Koornstra, Reinoud
2009-03-19 19:55 ` me22
2009-03-11 14:03 ` which glibc " Ian Lance Taylor
2009-03-11 19:29 ` Koornstra, Reinoud
2009-03-09 19:46 ` Koornstra, Reinoud [this message]
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=E92FAF79A8BBC642A36EEE3AA7F152D83CF384C325@GVW1089EXB.americas.hpqcorp.net \
--to=koornstra@hp.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).