VNC4.1.1 for Fedora
JAldrich "at" covista.com
Wed Aug 3 16:25:01 2005
What do I need to update in order to get my Fully-updated Fedora Core 3 box
to let me install VNC-server 4.1.1? What in the build-environment is causing
me to get a failed prerequisite of libstdc++.so.6?
I'd be happy if I could install your pre-compiled binary, as otherwise, I'm
going to have to go get the source for XOrg and a few other things just to
build a binary RPM so I can install vnc-server 4.1.1 on my Core 3 box.
I looked into getting compat-libstdc++ as Alasdair had suggested, but I'm
already running the latest version for Fedora Core 3:
[root "at" slave1 john]# rpm -q compat-libstdc++
So, I'm wondering what needs to be done to my box to get Real's 4.1.1 RPM
installed... Alternatively, who do I need to contact at Redhat/Fedora to get
them to build a backwards-compatible RPM?
Also, just wondering why the Real RPM will ONLY work on the latest and
greatest release of Fedora? Not everyone is going to want to upgrade every
time that Fedora releases a new version. Heck, I jumped straight from RedHat
9 to Fedora Core 3. I may skip 4 entirely, if reports of it being extremely
flaky don't subside... It would make better sense, in my opinion, if you're
going to release a binary-only RPM, to release a version that would work
with all currently supported releases of Fedora, i.e. Fedora 2, 3 and 4.
I would like to take a moment to say that while this could be misconstrued
as "bashing" Real or whining, I'm not intending it to come across that way.
I'm a little frustrated that I'm looking at having to upgrade my libstdc++
(and probably a LOT more due to dependencies) just to install the most
current release of VNC Server. I thought maybe by pointing out that
VNC-server 4.1.1 won't install on Fedora Core 3, I could get the attention
of the developers and maybe get them to release a "backwards-compatible"
version of VNC server 4.1.1. :-)