public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Avi Green <avi-nospam@sputnik7.com>
To: GCC Installation Help List <gcc-help@gcc.gnu.org>,
	libstdc++-v3 Development List <libstdc++@sourceware.cygnus.com>,
	Bernhard Rosenkraenzer <bero@redhat.com>
Subject: Re: Case history: Installing libstdc++ on i686-pc-linux-gnu (Red Hat)
Date: Wed, 29 Mar 2000 12:14:00 -0000	[thread overview]
Message-ID: <38E2650E.C3548ECF@sputnik7.com> (raw)
In-Reply-To: <38E1B1EA.DCF97B87@sputnik7.com>

I wrote:

> So:  What should I do?  Should I look for an old copy of the
> libstdc++-libc6.1-1.so.2 file on the 'net and just and paste it back
> into /usr/lib?  A good deal of the commands on my system require it.
> One idea: I observe that the gcc-c++ RPM info says that it "does
> include the static standard C++ library and C++ header files; the
> library for dynamically linking programs is available separately."
> Perhaps that would solve the problem?  Or is this something I can
> solve by pointing the libstdc++-libc6.1-1.so.2 symlink somewhere
> else or by setting LD_LIBRARY_PATH?

I found a non-RPM (finally!) copy of libstdc++-libc6.1-1.so.2 in the
Slackware distribution.  I copied it into /usr/lib, and my commands
seem to work fine now.  Using ldd(1), I determined that none of the
other missing library files are needed by my system except for
lib[cm].so.5 and libstdc++.so.27, and although the links with those
names were gone, fortunately the underlying files weren't, and I was
able to resolve all of the library dependency problems by putting
the files and links back into /usr/lib.  Hopefully this won't break
anything in the new libraries.  (Right?)

Thanks to everyone for listening.

--Avi


=========  Avi Green :) (: www.sputnik7.com  =========
========     Unix S/A & System Specialist     ========
========  avi at sputnik7.com   212 217-1147  ========

WARNING: multiple messages have this Message-ID
From: Avi Green <avi-nospam@sputnik7.com>
To: GCC Installation Help List <gcc-help@gcc.gnu.org>,
	libstdc++-v3 Development List <libstdc++@sourceware.cygnus.com>,
	Bernhard Rosenkraenzer <bero@redhat.com>
Subject: Re: Case history: Installing libstdc++ on i686-pc-linux-gnu (Red Hat)
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <38E2650E.C3548ECF@sputnik7.com> (raw)
Message-ID: <20000401000000.J9jfplr8AA5_QaOYDUIGRMOu5knqrgRjBOi-VJiUMjE@z> (raw)
In-Reply-To: <38E1B1EA.DCF97B87@sputnik7.com>

I wrote:

> So:  What should I do?  Should I look for an old copy of the
> libstdc++-libc6.1-1.so.2 file on the 'net and just and paste it back
> into /usr/lib?  A good deal of the commands on my system require it.
> One idea: I observe that the gcc-c++ RPM info says that it "does
> include the static standard C++ library and C++ header files; the
> library for dynamically linking programs is available separately."
> Perhaps that would solve the problem?  Or is this something I can
> solve by pointing the libstdc++-libc6.1-1.so.2 symlink somewhere
> else or by setting LD_LIBRARY_PATH?

I found a non-RPM (finally!) copy of libstdc++-libc6.1-1.so.2 in the
Slackware distribution.  I copied it into /usr/lib, and my commands
seem to work fine now.  Using ldd(1), I determined that none of the
other missing library files are needed by my system except for
lib[cm].so.5 and libstdc++.so.27, and although the links with those
names were gone, fortunately the underlying files weren't, and I was
able to resolve all of the library dependency problems by putting
the files and links back into /usr/lib.  Hopefully this won't break
anything in the new libraries.  (Right?)

Thanks to everyone for listening.

--Avi


=========  Avi Green :) (: www.sputnik7.com  =========
========     Unix S/A & System Specialist     ========
========  avi at sputnik7.com   212 217-1147  ========

  reply	other threads:[~2000-03-29 12:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.SOL.3.91.1000327114055.13734A-100000@cse.cygnus.com>
2000-03-27 14:52 ` Avi Green
2000-03-27 21:34   ` Case history: Installing libstdc++ on i686-pc-linux-gnu (RedHat) llewelly
2000-04-01  0:00     ` llewelly
2000-03-28 12:44   ` Case history: Installing libstdc++ on i686-pc-linux-gnu (Red Hat) Alexandre Oliva
2000-03-28 23:30     ` Avi Green
2000-03-29 12:14       ` Avi Green [this message]
2000-04-01  0:00         ` Avi Green
2000-04-01  0:00       ` Avi Green
2000-04-01  0:00     ` Alexandre Oliva
2000-04-01  0:00   ` Avi Green

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=38E2650E.C3548ECF@sputnik7.com \
    --to=avi-nospam@sputnik7.com \
    --cc=bero@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=libstdc++@sourceware.cygnus.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).