This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libio/stdio-lock.h should not be in egcs/libio
- To: drepper at ipd dot info dot uni-karlsruhe dot de
- Subject: Re: libio/stdio-lock.h should not be in egcs/libio
- From: hjl at lucon dot org (H.J. Lu)
- Date: Fri, 12 Sep 1997 14:01:08 -0700 (PDT)
- Cc: egcs at cygnus dot com
>
> hjl@lucon.org (H.J. Lu) writes:
>
> > libio/stdio-lock.h in egcs/libio doesn't look right. It
> > is a platform-dependent file. It should be generated by
> > gen-params or something like it.
>
> I haven't installed it this way. What I have in libstdc++'s libio are
> a collection of appropriate include files and the configure script
> makes sure the correct file is selected for the platform (with a dummy
> file as default). So I assume somethin is wrong with the egcs copy.
>
Since the egcs's libio doesn't use any MT-safe stuff, you
won't see any probelms. When I applied my MT-sfae patch,
it doesn't work due to the dummy libio/stdio-lock.h.
BTW, how does the configure script in egcs figure out what
libio/stdio-lock.h should look like? When the other libio
is used, the same stdio-lock.h should be used also.
--
H.J. Lu (hjl@gnu.ai.mit.edu)