OK, looks like you're using a self-built GCC. The reference to the system G++ (/usr/bin/g++) for COLLECT_GCC is interesting: that might suggest a possible misconfiguration, and/or that the wrong binary is still being picked up for some phase of compilation, for some reason.
Maybe try one of the following: 1. Using the "official" build of 4.5.1-10ubuntu1 with -fno-strict- volatile-bitfields. 2. Adding "-v" to the CFLAGS/CXXFLAGS to see which binaries are actually being invoked. Sorry for being stubborn, but if that flag doesn't work as a workaround, we're back to square one... -- volatile int causes inline assembly build failure https://bugs.launchpad.net/bugs/675347 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
