From: Alexandre Oliva <aoliva@cygnus.com>
To: Avi Green <avi-nospam@sputnik7.com>
Cc: Benjamin Kosnik <bkoz@cygnus.com>,
libstdc++-v3 Development List <libstdc++@sourceware.cygnus.com>,
GCC Installation Help List <gcc-help@gcc.gnu.org>
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: <orpusekeqw.fsf@zecarneiro.lsd.ic.unicamp.br> (raw)
Message-ID: <20000401000000.nEosUaYeIBPVjFz78Vn5bisO4k9OUhUSh5Ljf4FCz4I@z> (raw)
In-Reply-To: <38DFE709.D9B51CBC@sputnik7.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Mar 27, 2000, Avi Green <avi-nospam@sputnik7.com> wrote:
> p.s. After I installed v3, I found that
> /usr/lib/libstdc++-libc6.1-1.so.2 had been removed. I couldn't find
> any reference to that file in the v3 source tree, but it could have
> been wiped by one of the 2.95.2 RPMs.
You should certainly arrange for this file not to be removed, even if
you upgrade libstdc++. Did you upgrade libstdc++ using RPM? There
must be a way to arrange for it to upgrade a package without removing
the previous version's libraries.
--
Alexandre Oliva Enjoy Guaraná, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me
next prev parent reply other threads:[~2000-04-01 0:00 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 ` Alexandre Oliva [this message]
2000-03-28 23:30 ` Case history: Installing libstdc++ on i686-pc-linux-gnu (Red Hat) Avi Green
2000-03-29 12:14 ` Avi Green
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=orpusekeqw.fsf@zecarneiro.lsd.ic.unicamp.br \
--to=aoliva@cygnus.com \
--cc=avi-nospam@sputnik7.com \
--cc=bkoz@cygnus.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).