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: hjl at lucon dot org (H.J. Lu)
- Subject: Re: libio/stdio-lock.h should not be in egcs/libio
- From: Ulrich Drepper <drepper at ipd dot info dot uni-karlsruhe dot de>
- Date: 12 Sep 1997 23:48:39 +0200
- Cc: egcs at cygnus dot com
- References: <m0x9cpw-0004ecC@ocean.lucon.org>
- Reply-To: drepper at ipd dot info dot uni-karlsruhe dot de (Ulrich Drepper)
hjl@lucon.org (H.J. Lu) writes:
> 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.
It will use MT stuff. There wil be no difference between the libio
versions.
> BTW, how does the configure script in egcs figure out what
> libio/stdio-lock.h should look like?
I don't see your problem. In all libio versions the same configure
scipt is used and this selects the appropriate header from the
selection we'll have. Just let me finish this before solving not yet
existing problems.
-- Uli
---------------. drepper@cygnus.com ,-. Rubensstrasse 5
Ulrich Drepper \ ,-------------------' \ 76149 Karlsruhe/Germany
Cygnus Solutions `--' drepper@gnu.ai.mit.edu `------------------------