[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #35483] ./configure does not accept --target
From: |
Mike Frysinger |
Subject: |
[bug #35483] ./configure does not accept --target |
Date: |
Fri, 29 May 2020 11:22:59 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; CrOS x86_64 13080.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4136.1 Safari/537.36 |
Follow-up Comment #5, bug #35483 (project avr-libc):
> > for documentation on the arguments, please see:
> >
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Specifying-Target-Triplets.html#Specifying-Target-Triplets
>
> According to this documentation, there are up to three systems involved with
cross-compilers:
>
> --build specifies the system which builds the toolchain.
>
> --host specifies the system which executes the toolchain.
>
> --target specifies the system which executes the code that the toolchain
generated.
>
> Thus, when building a toolchain on a linux which is meant to run on windows
to generate code for avr, the correct specification would be:
you're misreading the targets, and your subsequent characterization of them is
wrong. windows is *not* executing avr-libc, nor is avr-libc producing code.
hence your your --host=windows & --target=avr-libc are incorrect.
> BTW: while at it: the configure script also don't accept the target as a
TRIPLET. That is: configure will fail when the target is specified as
avr-XXX-YYY
exactly: libc's do not generate code. which is why --target isn't supported.
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/bugs/?35483>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/