Comment 10 for bug 1309060

Revision history for this message
Mike Purvis (mikepurvis) wrote :

I gave the gcc-arm-none-eabi package in Utopic a try, and it seems that the introduction of the libstdc++-arm-none-eabi-newlib package has restored the issues I was having with C++ builds: http://packages.ubuntu.com/utopic/devel/libstdc++-arm-none-eabi-newlib

For the purposes of fixing Trusty, I set up a PPA for myself and used backportpackage to release the Utopic versions of the compiler, binutils and newlib into Trusty:

https://launchpad.net/~mikepurvis/+archive/ubuntu/stm32/+packages

Now unfortunately, the GCC builds are failing for reasons which are not entirely apparent to me, and the critical /usr/include/newlib/c++/4.8/ path while present (via the backported libstdc++-arm-none-eabi-newlib) isn't on the default include path for the compiler. Note that the update-alternatives symlinks do seem to be configured correctly:

$ ls /etc/alternatives/ -la | grep newlib
lrwxrwxrwx 1 root root 19 Aug 21 14:20 gcc-arm-none-eabi-include -> /usr/include/newlib
lrwxrwxrwx 1 root root 29 Aug 21 14:20 gcc-arm-none-eabi-lib -> /usr/lib/arm-none-eabi/newlib

Anyhow, this isn't a final answer, but I just wanted to provide an update of some progress, if others are wanting to do any further work or investigation. I'd really like to have a PPA solution for a full C++ gnuarm on Trusty that doesn't rely on apt pinning.