https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64051
--- Comment #7 from Andrew Pinski ---
(In reply to Pierre Ossman from comment #6)
> Just to make sure I understand you perfectly. This is not supported:
>
> ../configure --build=A --host=B --target=B
By itself yes this is not supported.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64051
--- Comment #6 from Pierre Ossman ---
Just to make sure I understand you perfectly. This is not supported:
../configure --build=A --host=B --target=B
Instead you have to do:
../configure --build=A --host=A --target=B
Then use that to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64051
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64051
--- Comment #4 from Pierre Ossman ---
I assumed that this would be what happened:
Given --build=B --host=H and --target=T:
1. A gcc would be configured with --build=B --host=H --target=T and put in the
installation directory.
2. A second gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64051
--- Comment #3 from Pierre Ossman ---
libstdc++ compiles fine though, but the previous stage did indeed include a C++
compiler. But even with that requirement, it still seems a bit dangerous. What
if the previous compiler uses a different excepti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64051
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64051
--- Comment #1 from Andrew Pinski ---
As far as I know a Canadian cross requires the cross toolchain to that target
at least the same languages as the Canadian cross. This check is the same check
in libstdc++ also.
