Re: [Boost-testing] [QNX6] [config] Status report - comments please

From: David Abrahams (dave_at_[hidden])
Date: 2005-11-04 08:24:43

"John Maddock" <john_at_[hidden]> writes:

>>> Not wishing to point fingers but take a look at a file that caused me
>>> some bother: libs/python/src/converter/type_id.cpp. Tell me whether
>>> you
>>> consider the tests to be legal.
>
> Hmmm, well it may be a mistake I guess, the problem is cxxabi.h is not a 
> standard lib header so it's not unreasonable to have assumed that it would 
> be available even when using some other std lib.  My guess is that it *is* 
> available when using STLport or even the Dinkum lib with Intel C++ on linux 
> (because those get tested).  Is QNX doing something odd like suppressing the 
> normal include paths when using the dinkum lib?
>
> Whatever if this is a QNX specific problem then:
>
> # if (defined(__GNUC__) && __GNUC__ >= 3) && \
>    !(defined(__QNXNTO__) && !(defined(__GLIBCPP__) || defined(__GLIBCXX__)))
>
> Would do it.  I realise this is full of double negatives, but it's too early 
> to get my brain around the rearangement!

  !(x && y) <==> !x || !y
  !(x || y) <==> !x && !y

 # if (defined(__GNUC__) && __GNUC__ >= 3) && \
    (!defined(__QNXNTO__) || defined(__GLIBCPP__) || defined(__GLIBCXX__))

Though I'm not sure where you mean to apply this.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com