This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: bits/libc-lock.h and _LIBC

From: Ulrich Drepper <drepper at redhat dot com>
To: Thorsten Kukuk <kukuk at suse dot de>
Cc: libc-hacker at sources dot redhat dot com
Date: Mon, 04 Nov 2002 01:29:14 -0800
Subject: Re: bits/libc-lock.h and _LIBC
References: <20021021112734.A25309@suse.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thorsten Kukuk wrote:

> We install libc-lock.h into /usr/include/bits. But libc-lock.h is
> only useable, if it is compiled with -D_LIBC, which breaks now with
> libio.h.

What exactly fails?  And when did it change?  The header is in this form
installed on my systems and I have no problems using <libio.h>.


> I suggest the following patch, or is there any reason for the
> ifdef _LIBC around __libc_lock_t ? We don't do this for __libc_key_t
> and all the other definitions.

I've made the types opaque back when for a good reason.  I think it was
mainly the use in libstdc++ but also to prevent any kind of initializers.

- -- 
- --------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9xj3q2ijCOnn/RHQRAnX8AJ9wl29zf64OnXqvkXZWqneItRCaFQCghBRG
Ix7S2+hU1/KMnaW6RCdczBM=
=K3X3
-----END PGP SIGNATURE-----

Follow-Ups:
- Re: bits/libc-lock.h and _LIBC
  - From: Thorsten Kukuk

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]