[cfe-dev] Installing libc++

[Howard Hinnant]

On Apr 24, 2011, at 1:20 PM, Jean-Daniel Dupas wrote:

> 
> Le 24 avr. 2011 à 18:01, Howard Hinnant a écrit :
> 
>> On Apr 24, 2011, at 11:51 AM, Jon Kalb wrote:
>> 
>>> 
>>> Thanks Howard, you guessed right.
>>> 
>>> This is my testit result (summary):
>>> 
>>> ****************************************************
>>> Results for /Users/jonkalb/Documents/development/developement/libcxx/test:
>>> using Apple clang version 2.0 (tags/Apple/clang-138) (based on LLVM 2.9svn)
>>> Target: x86_64-apple-darwin10
>>> Thread model: posix
>>> with -std=c++0x -stdlib=libc++
>>> ----------------------------------------------------
>>> sections without tests   : 1
>>> sections with failures   : 153
>>> sections without failures: 910
>>>                     +   ----
>>> total number of sections : 1064
>>> ----------------------------------------------------
>>> number of tests failed   : 1221
>>> number of tests passed   : 3019
>>>                     +   ----
>>> total number of tests    : 4240
>>> ****************************************************
>>> 
>>> Is this what I should expect?
>> 
>> I would've expected significantly fewer test failures for clang -std=c++0x -stdlib=libc++:
>> 
>> ****************************************************
>> Results for /test:
>> using Apple clang version 2.0 (trunk 125236) (based on LLVM 2.9svn)
>> Target: x86_64-apple-darwin10
>> Thread model: posix
>> with -std=c++0x -stdlib=libc++ -arch x86_64 -U__STRICT_ANSI__ -I../include /usr/lib/libc++.dylib
>> ----------------------------------------------------
>> sections without tests   : 1
>> sections with failures   : 74
>> sections without failures: 989
>>                      +   ----
>> total number of sections : 1064
>> ----------------------------------------------------
>> number of tests failed   : 215
>> number of tests passed   : 4023
>>                      +   ----
>> total number of tests    : 4238
>> ****************************************************
>> 
> 
> Is it on purpose that the testit script didn't include the -U__STRICT_ANSI__ flags (this flag was added to buildit to workaround some issue in darwin headers).
> Adding this flag will lower the count of failed tests.
> 
> FWIW, I got this with a fresh build.
> 
> using clang version 3.0 (trunk 130088)
> Target: x86_64-apple-darwin10.7.3
> Thread model: posix
> with -std=c++0x -U__STRICT_ANSI__ -stdlib=libc++  
> ----------------------------------------------------
> sections without tests   : 1
> sections with failures   : 76
> sections without failures: 987
>                       +   ----
> total number of sections : 1064
> ----------------------------------------------------
> number of tests failed   : 217
> number of tests passed   : 4023
>                       +   ----
> total number of tests    : 4240
> 

Ah, yes good point.  Yes it is on purpose that the test script doesn't automatically include this flag.  I keep "scripts" around so that I can easily try different options:

export OPTIONS="-stdlib=libc++ -arch i386"
export OPTIONS="-stdlib=libc++ -arch x86_64"
export OPTIONS="-std=c++0x -stdlib=libc++ -arch i386 -U__STRICT_ANSI__"
export OPTIONS="-std=c++0x -stdlib=libc++ -arch x86_64 -U__STRICT_ANSI__"

The need for -U__STRICT_ANSI__ should be considered a temporary workaround.  I had forgotten about needing it, thanks for the reminder.  I'll bet that is what Jon is seeing.

Howard