Mark Post wrote: > I'm running into this same link error with a number of other packages. It's > really looking like something wrong with the interaction between gcc 2.95.3, > and glibc 2.2.5. :(
Ah, now that is certainly possible, given the close interaction between the libc I/O and libstdc++ I/O routines ... This particular combination of gcc and glibc unfortunately is one we never tested. I'm afraid I don't have the time right now to investigate what's going on in this combination. Is it possible for you to either downgrade to glibc 2.2.4 or upgrade to gcc 3.2(.1)? Those are the combinations that we can be reasonable sure are working ... Bye, Ulrich -- Dr. Ulrich Weigand [EMAIL PROTECTED]
