On Wednesday 28 May 2003 17:50, Paul Murray wrote:
Marnus thanks for the info. I wanted to make sure I wasn't doing something wrong. "more" and another program "marparse" are the programs that I need to get working...with marparse being the most important. I sent Alain a verbose strace of marparse so Alain could see what calls were being made and perhaps see where the code is behaving differently.
Paul
I looked more closely into the issue, and noticed that glibc 2.3 has changed the way how libc internal functions call other libc internal functions. Formerly, they would pick up zlibc's replacements, but they no longer do now (many libc function set up "hidden" definitions using the libc_hidden_def macro, that can no longer be overriden by outside programs).
Thus applications that direclty use open() continue to work with zlibc, but those that use fopen64() don't, because fopen64() now always calls libc's own open64, and never zlibc's.
I've notified Ulrich Drepper and Jakub Jelinek from the glibc development team about the issue; hopefully we'll be able to work out a solution together.
In the meantime, I'd suggest you downgrade to glibc 2.2
Regards,
Alain
_______________________________________________ zlibc mailing list zlibc@tux.org http://www.tux.org/mailman/listinfo/zlibc