https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82408
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Peter Bohning from comment #6)
> Well I can't say I understand why the host and the target would ever be
> different, but are you saying that I need to add another flag for something?
I can think of one.
You are building a cross compiler that will run on windows targeting an
embedded target but you are building on a linux box.
> I mean I never set the target, so it can't determine the target from the
> host? All the other packages seemed to be fine with just "--host"?
Just use --target= and not --host here.
So the question now becomes do you want a compiler that runs on x86_64 or
aarch64?
If you want one that runs on x86_64 just use --target.
If you want one that runs on aarch64 that targets aarch64, you need to first
build a (new) cross compiler that runs on x86_64 [because the target libraries
can only be built with the newer version of the compiler(7)] and then build one
that is configured with
--target= --host= .
