On Thursday 18 May 2006 06:15, James Weatherall wrote:
> Hal,
>
> Linux distributions normally provide a libc-libstdc++ compatibility
> package that provides the appropriate stubs & symlinks for older
> versions of the libraries - you should be able to search the packages
> for your distribution for the relevant filename in order to locate
> the package.

The only issue is I don't always have control over the distro that this 
will be installed on.  I was hoping there was some general rule, like 
link it to the lib that fits the wildcards "libstdc++-*libc*.so with 
the highest version number in place of the 2nd wildcard.  That way I 
could write a bash script (or, since most of the installer is in Java, 
I could do it in Java if it's too much for a script) that would list 
the directory and get the appropriate file name.

Hal

> Regards,
>
> Wez @ RealVNC Ltd.
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Hal Vaughan
> > Sent: 18 May 2006 07:07
> > To: [email protected]
> > Subject: Info on C Libraries that RealVNC Uses
> >
> > I am trying to install RealVNC on a number of different systems
> > that we'll be using.  There's no problem with Windows, but on
> > Linux, on a number of systems ask for libstdc++-libc6.2-2.so.3.  On
> > my system, that
> > file is a symlink to libstdc++-3-libc6.2-2-2.10.0.so.  As I
> > understand
> > that, it means that I can use a symlink like this in most
> > cases and not
> > have a problem.
> >
> > I'm not a C programmer, but from what I've gleaned, as long as the
> > symlink is to a late enough library there isn't a problem.
> > What I need
> > to do is work out an algorithm for what file I should symlink
> > to.  For
> > example, I don't know what the "3" in the 2nd filename represents
> > and if it is important.  If I can just list the library directories
> > with wildcards, get a list of files, and sort them so the last one
> > has the highest value, then link to that, it'd be great.
> >
> > What are the rules for these types of symlinks?  Should I
> > just look for
> > any version of the library that is the same or greater?  Do I pay
> > attention to the version numbers after the "++-" and before
> > the "libc"?
> > Or do I only have to pay attention to the numbers after
> > "libc" and the
> > ".so" at then end?
> >
> > What criteria do I use to try to determine which file I
> > should symlink
> > to?
> >
> > Thanks for any help on this!
> >
> > Hal
> > _______________________________________________
> > VNC-List mailing list
> > [email protected]
> > To remove yourself from the list visit:
> > http://www.realvnc.com/mailman/listinfo/vnc-list
>
> _______________________________________________
> VNC-List mailing list
> [email protected]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to