https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
--- Comment #7 from Peter A. Bigot pab at pabigot dot com ---
DEAR PEOPLE FROM THE FUTURE:
The problem is that OpenEmbedded used target-specific flags to build the
libraries, but did not ensure that the compiler was configured to default to
the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
Peter A. Bigot pab at pabigot dot com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
Jonathan Wakely redi at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
--- Comment #2 from Peter A. Bigot pab at pabigot dot com ---
Thanks. The compiler and libstdc++ are built using Yocto's standard recipe for
the beaglebone. Obviously there's something wrong with it; what that would be
is not obvious and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
--- Comment #3 from Jonathan Wakely redi at gcc dot gnu.org ---
It might be obvious in the output of 'gcc -v'.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
--- Comment #4 from Peter A. Bigot pab at pabigot dot com ---
It's not obvious to me:
beaglebone[98]$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/gcc/arm-poky-linux-gnueabi/4.9.1/lto-wrapper
Target:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
Jonathan Wakely redi at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |UNCONFIRMED
