From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17809 invoked by alias); 26 Mar 2004 13:16:56 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 17800 invoked from network); 26 Mar 2004 13:16:54 -0000 Received: from unknown (HELO smtp-relay-7.sea.adobe.com) (192.150.22.7) by sources.redhat.com with SMTP; 26 Mar 2004 13:16:54 -0000 Received: from inner-relay-1.corp.adobe.com (inner-relay-1 [153.32.1.51]) by smtp-relay-7.sea.adobe.com (8.12.10/8.12.10) with ESMTP id i2QDGpSP022739; Fri, 26 Mar 2004 05:16:51 -0800 (PST) Received: from iplan-mn (iplan-mn.corp.adobe.com [130.248.25.5]) by inner-relay-1.corp.adobe.com (8.12.9/8.12.9) with ESMTP id i2QDGm3k026758; Fri, 26 Mar 2004 05:16:49 -0800 (PST) Received: from mn-eljayet.adobe.com (b-25-160.corp.adobe.com [130.248.25.160]) by iplan-mn.corp.adobe.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0HV600AAZQ7Z7E@iplan-mn.corp.adobe.com>; Fri, 26 Mar 2004 07:16:47 -0600 (CST) Date: Fri, 26 Mar 2004 13:39:00 -0000 From: Eljay Love-Jensen Subject: RE: noreentrant functions on Linux Advance Server 2.1 using gcc 2.96 In-reply-to: <2B721C6525F0D411B1E900B0D0226BDD044C73E1@mohmsg01.ad.infos ys.com> X-Sender: eljay@iplan-mn.corp.adobe.com To: Jyotirmoy Das Cc: gcc-help@gcc.gnu.org Message-id: <6.0.3.0.2.20040326065648.01f62ad8@iplan-mn.corp.adobe.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT References: <2B721C6525F0D411B1E900B0D0226BDD044C73E1@mohmsg01.ad.infosys.com> X-SW-Source: 2004-03/txt/msg00283.txt.bz2 Hi Jyotirmoy, I do not know if that list is comprehensively sufficient for Red Hat Linux Advanced Server 2.1. (I use RHLAS 2.1, but not for a multithreaded application.) I presume you are including the correct flag for multithreading. That would be "gcc -pthread" for compile and link (which puts in -D_REENTRANT and -lpthread, respectively). Da? Nyet? And I presume your GCC was built with --enable-threads=posix (which you can see via "gcc -v" for GCC 3.2, but I presume you'll have to infer during compilation if you use RH/GCC 2.96). In C and C++, multithreading is wishy-washy. It's not part of the language, it's a "bolt-on" that varies by vendor. And not all vendors or platforms support POSIX (or necessarily support POSIX correctly). For C++, I believe the BOOST folks have a platform-neutral thread API. Assuming you were using C++, it's probably a little late in the game to switch horses to a different thread paradigm (say, BOOST versus POSIX or versus platform-centric). HTH, --Eljay