From: awesome-dave1@juno.com
To: blinux-list@redhat.com
Subject: viavoice suggestion, not for the undaring
Date: Mon, 19 May 2003 21:18:30 -0400 [thread overview]
Message-ID: <20030519.211830.528.0.awesome-dave1@juno.com> (raw)
Hello,
I lost my nerve on this, there were to many dependencies involved and it
seemed like the rewards would be to slim and the risks much to great. I
checked the compat-libstdc++ and -devel library versions from rh8 and
rh9. There is a difference, my idea was to remove the 9 compatibility
libs and put in the 8 ones. I would not force them, but would manually
remove their dependencies until each of them removed cleanly, then put in
the 8 libs and restore the previously removed 9.0 dependencies. If anyone
tries this, be aware that one of the dependencies of the -devel package
was gcc-c++ and i was not daring enough to continue with this. I wish IBM
would revamp this project!!!
Dave.
________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!
reply other threads:[~ 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=20030519.211830.528.0.awesome-dave1@juno.com \
--to=awesome-dave1@juno.com \
--cc=blinux-list@redhat.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).