Date: Thu, 21 Mar 2002 09:52:35 -0700 (MST) From: "John E. Hein" <jhein@timing.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/36167: _THREAD_SAFE & _REENTRANT used inconsistently Message-ID: <200203211652.g2LGqZH50416@Elmer.timing.com>
next in thread | raw e-mail | index | archive | help
>Number: 36167 >Category: bin >Synopsis: _THREAD_SAFE & _REENTRANT used inconsistently >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Mar 21 09:00:02 PST 2002 >Closed-Date: >Last-Modified: >Originator: John E. Hein >Release: FreeBSD 4.5-RELEASE >Organization: Timing Solutions Corporation >Environment: System: -STABLE & -CURRENT >Description: stdio.h uses _THREAD_SAFE math.h & openssl/e_os.h use _REENTRANT On linux, _THREAD_SAFE & _REENTRANT are documented to be synonymous (in /usr/include/features.h). I don't know what POSIX has to say on the issue (although it looks like they use _POSIX_THREAD_SAFE_FUNCTIONS - see comment in unistd.h). Of course, _REENTRANT is not mentioned in gcc(1) whereas _THREAD_SAFE is. >How-To-Repeat: egrep -r '_REENTRANT|_THREAD_SAFE' /usr/include >Fix: Until a possibly better, more posix compliant, solution comes along, either: - Have headers use just _THREAD_SAFE or _REENTRANT or - Have headers use treat _THREAD_SAFE or _REENTRANT the same. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203211652.g2LGqZH50416>