Re: [Boost-testing] attn: eslbaer gcc-4.7 test runner

Subject: Re: [Boost-testing] attn: eslbaer gcc-4.7 test runner
From: Eric Niebler (eric_at_[hidden])
Date: 2012-07-28 19:54:03

On 7/27/2012 10:16 AM, Eric Niebler wrote:
> To whomever runs the "eslbael gcc-4.7" tests against trunk. I'm curious
> about this failure:
> 
> http://beta.boost.org/development/tests/trunk/developer/output/eslbaer-boost-bin-v2-libs-xpressive-test-c_traits-test-gcc-4-7-debug-link-static.html
> 
> What standard library are you using? It seems to be some variant of
> glibc that doesn't have an __isctype function. I've never encountered
> that before. Can you tell me how the ctype classification routines are
> implemented? Usually, things like (the C api) isalpha and isdigit are
> implemented in terms of a lower-level primitive like __isctype. I'll
> also need to know how to detect that particular std library so I know
> when to use __isctype vs. something else.

Disregard. I was able to reproduce the problem in my Linux VM and work
around it. Looks like a recent change in glibc which is starting to
infect all the Linux gcc test runners.

-- 
Eric Niebler
BoostPro Computing
http://www.boostpro.com