Well actually, when I just let it do its stuff, it worked fine...
I bought ApplixWare for Linux this weekend and went to install it.
Now, I've got SuSE 6.0 installed which is apparently libc6 (glibc). So I
was a bit surprised to discover Applix trying to install its libc5
version when there's a libc6 version just sitting there.
It turns out that one of its criteria for determining that this is a
libc6 system, is to look for /usr/lib/libstdc++.so.2.8. This doesn't
exist in SuSE 6.0 - it has libstdc++ 2.7 and libstdc++ 2.9, but not 2.8.
First I tried to just create a symlink from version 2.9 to version 2.8,
and Applix installed the libc6 version, but failed to work due to
unresolved symbols. Then I tried to find a libstdc++ 2.8, but found that
very difficult, finally found sources to 2.8.1 and 2.8.1.1 but they
failed to make (compiler errors, looks like errors in the source code).
This of course might be why SuSE doesn't include them :-)
But anyway, I reverted and just let it install the libc5 version and it
works fine, but it would be nice to be able to know I could install
libc6 software.
It would be even nicer if Applix didn't depend upon internal library
symbols so one could use it with newer versions of the libraries it
uses... I'll be moaning to them about this. :-)
--
Rachel Greenham
Epinet Communications plc
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
