From: Beecher Greenman <rbg6038@ritvax.isc.rit.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: EGCS upgrade?
Date: Sun, 31 Jan 1999 22:35:53 -0500 [thread overview]
Message-ID: <01J77GMEJG9Q9JDPMS@ritvax.isc.rit.edu> (raw)
I tried upgrading to EGCS 1.0.3 using the RPM on biggi.linuxppc.org. It
didn't work, so I tried uninstalling it and reinstalling with the
original RPM's, but that appears to have fried my libstdc++, which among
other things keeps Netscape from working. I'm trying to upgrade EGCS as
high as I can, since I want to try running Kernel 2.2.1 (anyone have a
prebuilt kernel out there, by any chance?)
Compiiling from the Cygnus sources for 1.1.1 didn't seem to work; there
were more than a few errors when I tried (and that's really a shame; I
was reading that 750 support was just added and I wanted to try that one
out).
Anyway, what's the best way to upgrade my EGCS installation past the 1.0
on biggi? For that matter, where can I find another copy of libstdc++; I
didn't see any RPM's on biggi that might have it. Thanks!
-Beecher Greenman
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next reply other threads:[~1999-02-01 3:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-01 3:35 Beecher Greenman [this message]
1999-02-01 6:02 ` EGCS upgrade? Cort Dougan
1999-02-01 9:54 ` Martin Costabel
1999-02-01 15:07 ` Nathan Ingersoll
1999-02-01 17:37 ` Cort Dougan
1999-02-01 18:05 ` nathan ingersoll
-- strict thread matches above, loose matches on Subject: below --
1999-02-03 5:10 Beecher Greenman
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=01J77GMEJG9Q9JDPMS@ritvax.isc.rit.edu \
--to=rbg6038@ritvax.isc.rit.edu \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).