delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/03/20/08:02:14

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3AB7550E.4C86E21@mip.sdu.dk>
Date: Tue, 20 Mar 2001 14:03:10 +0100
From: =?iso-8859-1?Q?Ren=E9=20M=F8ller?= Fonseca <fonseca AT mip DOT sdu DOT dk>
Organization: MIP, University of Southern Denmark
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Cygwin-Mailing-List <cygwin AT cygwin DOT com>
Subject: gcc --enable-threads

Hi,

Is the gcc-2.95.2 package configured/built with "--enable-threads"?

If this isn't the case that could explain why my multi-threaded C++
applications fail. According to gcc.gnu.org "--enable-threads"
influences the exception handling mechanism for C++. Is there a reason
why "--enable-threads" isn't used?

René

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019