This fails with g++-4.6.1-4 from testing at the same place.
I've updated the packages in sourceforge, so no patches are needed. I've attached a revised build.sh which runs the tests with the current versions. I was about to dive into a rant about "why didn't you try this before releasing gcc/g++ 4.6.1-4" when I spotted a bug in v3c's build system, now fixed. If you'd tried it yourself you could have let me know. Shouldn't incorrect code generation block a compiler release? Please try this one. Philip
build.sh
Description: Bourne shell script
