From: Frank Schafer <frank.schafer@setuza.cz>
To: help-gcc@gnu.org
Subject: GCC3.0.3 libs
Date: Tue, 19 Feb 2002 22:25:00 -0000 [thread overview]
Message-ID: <1014186309.7069.40.camel@ADMIN> (raw)
Hi there,
During my experiments with this version of GCC, I discovered something
very interesting.
I configured with the --enable-version-specific-runtime-libs. The
configure/build/indtall went fine.
Then I changed into /v_dsk/gcc-new ( the --prefix ).
Changing further into lib/gcc-lib/i686-pc-linux-gnu/3.0.3 I'm in the dir
containing libstdc++.
Now I did an ``ldd'' over this lib and got:
libgcc_s.so.1 => not found
hmmm ... this lib is ( beneath libstdc++ ) in
$(prefix)/lib/gcc-lib/i686-pc-linux-gnu/3.0.3 . Will I in fact have to
have such a thing in my ld.so.conf?
I was wondering about, if I could make gcc3 my standard compiler. Now
I've removed the whole gcc3 tree.
Is there a possibility to make gcc3 behave as the 2.95.x branch did?
Regards
Frank
reply other threads:[~2002-02-20 6:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1014186309.7069.40.camel@ADMIN \
--to=frank.schafer@setuza.cz \
--cc=help-gcc@gnu.org \
/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).