From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11986 invoked by alias); 23 Nov 2005 09:26:01 -0000 Received: (qmail 11973 invoked by uid 48); 23 Nov 2005 09:25:59 -0000 Date: Wed, 23 Nov 2005 09:26:00 -0000 Message-ID: <20051123092559.11972.qmail@sourceware.org> From: "stefan dot puiu at gmail dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20051119151517.1890.stefan.puiu@gmail.com> References: <20051119151517.1890.stefan.puiu@gmail.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/1890] strerror() unnecessarily non thread-safe X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00114.txt.bz2 List-Id: ------- Additional Comments From stefan dot puiu at gmail dot com 2005-11-23 09:25 ------- Oh, and about "picking the stupid definition", I specifically pointed you to a post on the autoconf mailing list. Here's a quote: "You would be best served by using configure to learn how the default strerror_r behaves and adapting your code to suit. You don't want to force -D_XOPEN_SOURCE=600 on all systems because behavior when the system does not support this level is undefined. In my experience, headers on some systems fail miserably if you specify an _XOPEN_SOURCE value greater than what they were designed to expect. Using -D_XOPEN_SOURCE=500 is reasonably safe on most (but not all) systems. Trying to force the headers to behave a particular way seems to be a lost cause. After trying this approach for a number of months, I finally realized that relying on default behavior worked best." -- http://sourceware.org/bugzilla/show_bug.cgi?id=1890 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.