Bruce Dubbs writes:
>> Is there a way to disable the testing of it? Though I've only used
>> mudflap on non-linux platforms, I'd hate to see the old thing go away.
>
> Sure. We could just remove the only test that fails:
>
> mv ./libmudflap/testsuite/libmudflap.c++/pass41-frag.cxx \
> ./lib
Billy O'Connor wrote:
> Bruce Dubbs writes:
>> I am wondering if we ought to disable building libmudflap using the
>> obscure option --disable-libmudflap (It's not in configure's --help).
>>
>> This would eliminate a lot of questions about check failures. I doubt
>> that it is used very often and
Bruce Dubbs writes:
> I am wondering if we ought to disable building libmudflap using the
> obscure option --disable-libmudflap (It's not in configure's --help).
>
> This would eliminate a lot of questions about check failures. I doubt
> that it is used very often and it does seem to give some
I've been looking at the gcc checks. The only failures I see that I
can't explain are all associated with libmudflap:pass41-frag.cxx. This
test fails if any optimization is used.
It is really very simple:
int
main (int argc, char *argv[])
{
std:string myStr = "Hello, World!";
std:co
