[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: shared libraries and _REENTRANT



On Sun, Jun 24, 2007 at 01:50:51AM -0700, Russ Allbery wrote:
> Felipe Sateler <fsateler@gmail.com> writes:
> > Felipe Sateler wrote:
> >> Policy 10.2 says we must compile shared libraries with -D_REENTRANT:
> 
> >>> You must specify the gcc option -D_REENTRANT when building a library
> >>> (either static or shared) to make the library compatible with
> >>> LinuxThreads.
> 
> >> However, LinuxThreads has been superseeded by NPTL. Is this still
> >> necessary?
> 
> > Some googling shows that _REENTRANT is necessary for POSIX threading, so
> > it should be still needed.
> 
> This just came up at DebConf, and our belief is that it's only needed to
> get prototypes for a few functions that aren't prototyped otherwise.  That
> would imply that if your software is building without undeclared function
> warnings, you don't need it.

  exactly, at least in the glibc, _REENTRANT is vaguely used to enable
some obscure functions. It has absolutely no impact else (especially no
function are diverted that way with recent libc's at least -- aka at
least since etch).

  Note that this macro is documented in features.h and
feature_test_macros(7).

Cheers,

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: pgpufCCIwDFdC.pgp
Description: PGP signature


Reply to: