Timeline for gcc cross compilation fails
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 30, 2017 at 19:08 | answer | added | Tarjei T. Jensen | timeline score: 0 | |
| Jun 14, 2017 at 21:32 | comment | added | Jay | @StephenKitt. I tried removing --enable-libstdcxx-pch, but that did not make any difference. | |
| Jun 14, 2017 at 7:38 | comment | added | Stephen Kitt | I suspect --enable-libstdcxx-pch is the option causing problems here; could you try without that? | |
| Jun 2, 2017 at 23:10 | history | edited | Jay | CC BY-SA 3.0 | added 1069 characters in body |
| Jun 2, 2017 at 22:40 | comment | added | Jay | Building gcc 4.9.4. The configure arguments are the same as those that the previous compiler used (gcc -v output). I think the '--enable-cheaders=c_std' has something to do with it. As a work-around, I can copy the (missing) files (ccomplex cfenv cinttypes cstdalign cstdbool cstdint ctgmath) from libstdc++-v3/include/c_global/ to libstdc++-v3/include/c_std so the generated symlinks are not broken. The build completes. Still, if --enable-cheaders=c_std is configured, why would it try to compile code including headers not in c_std? | |
| Jun 2, 2017 at 20:16 | history | tweeted | twitter.com/StackUnix/status/870735831945924609 | ||
| Jun 2, 2017 at 18:15 | comment | added | Stephen Kitt | Which version of GCC are you building? What ./configure arguments are you using? | |
| Jun 2, 2017 at 17:50 | history | asked | Jay | CC BY-SA 3.0 |