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 11:19:13 -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:
>
> > 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.
>
> There certainly can be problems like this. But the only other library
> which knows about FILE internals is libstdc++. So keeping this in
> sync with libc should be sufficent.
I don't think so. Say we have
extern FILE *fp;
In libx.so, we have
fp = fopen (.....);
In liby.so, we have
fclose (fp);
Can you tell me which fopen/fclose are used, Old or new?
--
H.J. Lu (hjl@gnu.org)