This is the mail archive of the
libc-hacker@sourceware.cygnus.com
mailing list for the glibc project.
Re: bincompat problem with 2.0.102 (StarOffice 5)
- To: drepper@cygnus.com
- Subject: Re: bincompat problem with 2.0.102 (StarOffice 5)
- From: hjl@lucon.org (H.J. Lu)
- Date: Mon, 16 Nov 1998 10:29:43 -0800 (PST)
- Cc: tmrini@ntplx.net, aj@arthur.rhein-neckar.de, libc-hacker@cygnus.com (GNU C Library)
>
> hjl@lucon.org (H.J. Lu) writes:
>
> > > Program received signal SIGSEGV, Segmentation fault.
> > > 0x4015b45d in _IO_old_file_close_it (fp=0x8067f08) at oldfileops.c:140
> > > 140 close_status = _IO_SYSCLOSE (fp);
> > >
> > > I've attached the strace output (if the list doesn't eat it..).
> > >
> >
> > You may have to make sure all the libraries used by SO 5.0 are compiled
> > with the same glibc. Otherwise, you may wind up calling the wrong libio
> > functions. Ulrich, does that make any senee?
>
> I don't expect any libio related compatibility problems anymore. If
> the package is compiled against the normal glibc 2.0 the old functions
> should be called.
>
What if
1. foo uses libx.so and liby.so.
2. libx.so is compiled against glibc 2.0.
2. liby.so is compiled against glibc 2.1.
I think foo will have a problem with libio routines if FILE * is used
between libx.so and liby.so.
H.J.