The pre-requisites could be different for different OSes. Plus
architecture matters, architecture basically corresponds to the
underlying hardware that you would be running a RPM's delivered binaries
or libraries. One can certainly download source RPMs and compile them
for various OSes and underlying hardware architecture that it's going to
run. This is a general idea from my side.
Ken Failbus
Vinay Venkataraghavan wrote:
Hi guys,
Thanks for your replies. I think the problem as Sean
said was that I was trying to upgrade using the -U
option rather than just install it.
I have one other question. Does the distribution an
rpm comes from matter. For instance if I have an rpm
that is available from Conectiva, can I use it on Red
hat. It seems to me that only the architecture would
matter right?
Thanks,
Vinay
--- Sean Sosik-Hamor <sean@xxxxxxxxxxxxxxx> wrote:
On May 24, 2005, at 06:33 PM, Wichmann, Mats D
wrote:
How can I upgrade libstdc++.so.5 to
libstdc++.so.6
In general, a libstdc++.so.6 ought to be able to
/coexist/ with (not replace) libstdc++.so.5.
That's
what the library versioning scheme is for, after
all.
Correct. Try rpm -ivh foo.rpm instead of rpm -Uvh
foo.rpm. Many RPMs
will allow multiple versions to happily coexist as
long as there are
no conflicting files trying to overwrite each other.
Our product is
running both 5 and 6 side by side with no ill
effects.
/Sean/
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
begin:vcard
fn:Ken Failbus
n:Failbus;Ken
org:Ulticom, Inc.
adr:;;1015 Briggs Road;Mt. Laurel;NJ;08054;USA
email;internet:ken.failbus@xxxxxxxxxxx
tel;work:(856) 787-2789
url:http://www.ulticom.com
version:2.1
end:vcard
