hehe :) slower machines ? hehe :) I just went from a 486/100 16MB to a
K6 II 333 32MB a few months ago, but I like to add more RAM, how did you
know that ? :-)
> > and since I'm on the subject of SuSE 6.1, I really like to know whether
> > owners of the official SuSE 6.1 have problems reading word97-doc's.
>
> What errors are you getting? If you build AbiWord yourself, you can
> enable debug messages ("export ABI_OPT_DEBUG=1 ; make") to see
I'll do that (again:).
> all the things the Word importer tries when decoding it. It's
> possible it just says "this is a Word 95 document" and quits. The
> importer right now only does Word 97.
I tried the word97-testfile from the abi-0.5.5 source.
and it says something like "this is a plain text file".
> > SuSE 6.1-eval. *still* refuses to read them here (though I must admit that
> > I've used libstdc++.so.2.8 from Redhat 5.2 to get it running, I'll try to
> > find a SuSE 6.1 one, if any.).
>
> We really shouldn't need libstdc++.so.2.8 to run the binary. If it's
> in one of the packages as a dependency, it's a bug in the package.
so, it is, SuSE 6.1-eval complained about it.
> If it were GCC needing the .a to compile, that might be different (then
> it's a bug in the code, we shouldn't need libstdc++ at all).
> A quick ldd shows:
>
> sterwill@lister [bin] ldd AbiWord_d
> libdl.so.2 => /lib/libdl.so.2 (0x40011000)
> libpng.so.2 => /usr/local/lib/libpng.so.2 (0x40014000)
> libz.so.1 => /usr/lib/libz.so.1 (0x4003c000)
> libgtk-1.2.so.0 => /usr/local/lib/libgtk-1.2.so.0 (0x4004c000)
> libgdk-1.2.so.0 => /usr/local/lib/libgdk-1.2.so.0 (0x40164000)
> libgmodule-1.2.so.0 => /usr/local/lib/libgmodule-1.2.so.0
> (0x40195000)
> libglib-1.2.so.0 => /usr/local/lib/libglib-1.2.so.0 (0x40199000)
> libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x401bb000)
> libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x401c7000)
> libm.so.6 => /lib/libm.so.6 (0x4026a000)
> libc.so.6 => /lib/libc.so.6 (0x40283000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
very very strange...
[root@onderste /root]# rpm -qf /usr/bin/X11/AbiWord_d
abisuite-0.7.0-1
[root@onderste /root]# ldd /usr/bin/X11/AbiWord_d
libdl.so.2 => /lib/libdl.so.2 (0x40008000)
libpng.so.2 => /usr/lib/libpng.so.2 (0x4000b000)
libz.so.1 => /usr/lib/libz.so.1 (0x40025000)
libstdc++.so.2.8 => /usr/lib/libstdc++.so.2.8 (0x40034000)
libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x40075000)
libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x40197000)
libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x401c9000)
libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x401cc000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x401ee000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x401fa000)
libm.so.6 => /lib/libm.so.6 (0x4029d000)
libc.so.6 => /lib/libc.so.6 (0x402b6000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)
[root@onderste /root]# rpm -V abisuite
[root@onderste /root]#
libstdc++.so.2.8 is there again ... 8-?
> > I also tried building AbiWord on SuSE 5.3-eval and Caldera OpenLinux 1.3,
> > but both of them don't support glibc, so I've rejected that idea.
>
> libc5 machines should work fine. My machine at home is running
hmmm, strange, there was a *clear* error about GLIBC from the build on both
of them, of course I can reproduce it (I should have saved the log).
> libc 5.4.38 on some old Slackware variant. I can build and run AbiWord
Slackware is a little bit different, 3.6 and 4.0 are still libc5 according
to the FAQ on www.slackware.org (by accident I just read it tonight),
but are said to have support for glibc to run (and build ??).
It must be a really old Slackware then. What Slackware-version is it ?
> fine, but my compiler (EGCS 1.1.2) doesn't seem to build libpng
> correctly
> so documents with PNG images segfault. It's a problem with libpng at
> all
> levels (gimp, imlib, xv all don't work). Maybe it's my C library
> and not my compiler... don't know, and will probably reformat soon
> enough.
hmmm, that's on Debian I guess ?
Redhat 5.2: egcs-2.90.29 980515 (egcs-1.0.3 release)
maybe too bleeding-edge ? ;-)
-- - greetings, Albert - -- I doubt, therefore I might be.