Library versions (libg++2.7.2/libc6.1-1)

2001-07-16 Thread Dave Sherohman
I'm trying to install some software whose installer wants to see
libstdc++-libc6.1-1.so.2, libg++.so.2.7.2, and libstdc++.so.27.
I've installed libg++27 and symlinked those libraries from
/usr/lib/libc5-compat to /usr/lib and /usr/lib/libstdc++-libc6.1-2.so.3
to libstdc++-libc6.1-1.so.2.

Needless to say, this segfaults the installer, but those are the closest
I've been able to find to the required versions.  (libg++27 claims
that libg++272 is the libc6 package, but neither 'apt-cache show'
nor debian.org's web search can find any evidence of a libg++272 aside
from that statement.)

I assume that debs exist of these libraries, even though they may be
considered obsolete.  Where can I find them?  If not, what's my best
bet for getting this piece of sh^Hoftware up and running?



Re: Library versions (libg++2.7.2/libc6.1-1)

2001-07-16 Thread Jimmy Richards
On Mon, Jul 16, 2001 at 11:19:53AM -0500, Dave Sherohman wrote:
 I'm trying to install some software whose installer wants to see
 libstdc++-libc6.1-1.so.2, libg++.so.2.7.2, and libstdc++.so.27.
 I've installed libg++27 and symlinked those libraries from
 /usr/lib/libc5-compat to /usr/lib and /usr/lib/libstdc++-libc6.1-2.so.3
 to libstdc++-libc6.1-1.so.2.

Hi,

I think you need to install the package 'libstdc++2.9-glibc2.1'. It
installs a symlink

libstdc++-libc6.1-1.so.2 - libstdc++-2-libc6.1-1-2.9.0.so

HTH,

Jim Richards

 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


binZseAVXcCDM.bin
Description: PGP Key 0x0062D7A7.


pgpmxaT0VsP4w.pgp
Description: PGP signature


Re: Library versions (libg++2.7.2/libc6.1-1)

2001-07-16 Thread Dave Sherohman
On Mon, Jul 16, 2001 at 11:31:04AM -0600, Jimmy Richards wrote:
   I think you need to install the package 'libstdc++2.9-glibc2.1'. It
 installs a symlink
 
 libstdc++-libc6.1-1.so.2 - libstdc++-2-libc6.1-1-2.9.0.so

Nope, that didn't do it.  The installer still segfaults, presumably
because it doesn't like having libg++ linked against libc5.