https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
--- Comment #7 from Peter A. Bigot ---
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 corresponding architect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
Peter A. Bigot changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
Jonathan Wakely changed:
What|Removed |Added
Status|WAITING |UNCONFIRMED
Ever confirmed|1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
--- Comment #4 from Peter A. Bigot ---
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: arm-poky-linux-gnueabi
Configured w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
--- Comment #3 from Jonathan Wakely ---
It might be obvious in the output of 'gcc -v'.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
--- Comment #2 from Peter A. Bigot ---
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 probably isn't a gcc problem.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62100
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
