X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<49F81E85.3080802@gmail.com>
Date:	Wed, 29 Apr 2009 10:31:49 +0100
From:	Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent:	Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: GCC 4.4.0 - Can't activate threading support
References:	<23292063 DOT post AT talk DOT nabble DOT com> <49F817C2 DOT 2000908 AT gmail DOT com> <23293465 DOT post AT talk DOT nabble DOT com>
In-Reply-To:	<23293465.post@talk.nabble.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Casull wrote:

> I am basically trying to take advantage
> of the C++0x implementation provided by GCC 4.4 through the <thread> header
> for example. The GCC 4.4 implementation of std::thread is guarded by the
> following preprocessing directive:
> 
>    #if defined(_GLIBCXX_HAS_GTHREADS) &&
> defined(_GLIBCXX_USE_C99_STDINT_TR1)
> 
> When looking at the bits/c++config.h, _GLIBCXX_USE_C99_STDINT_TR1 is defined
> but _GLIBCXX_HAS_GTHREADS isn't.

  Ah.  There is an autoconf test in libstdc++-v3 that defines that, and the
comment says:

> dnl Check if gthread implementation defines the types and functions
> dnl required by the c++0x thread library.  Conforming gthread
> dnl implementations can define __GTHREADS_CXX0X to enable use with c++0x.

> Either I am not passing the correct flags to GCC (in addition to the
> -std=c++0x) or my installation of gcc is not correct, or last possibility,
> my GCC build configuration is not correct.

  Well, I think there's  one other possibility: Cygwin (or perhaps the newlib
core) don't define or support all the "types and functions required by the
c++0x library".  I'll take a look and see if I can find out why it would fail.

    cheers,
      DaveK





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -