[bug #35483] ./configure does not accept --target

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[bug #35483] ./configure does not accept --target

Kevin Cuzner-2
URL:
  <http://savannah.nongnu.org/bugs/?35483>

                 Summary: ./configure does not accept --target
                 Project: AVR C Runtime Library
            Submitted by: rolf_ebert
            Submitted on: Mi 08 Feb 2012 17:14:26 MET
                Category: Build Infrastructure
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build system
                  Status: None
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 1.8.0
           Fixed Release: None

    _______________________________________________________

Details:

I didn't build avr-libc so I don't know when this (mis)feature appeared...

The top level configure script requires to spell out --host=avr. IMHO this is
unfortunate for several reasons:

1) the product is called avr-libc. I wouldn't expect it to provide anything
else (e.g. a libc for ARM) than a libc for avr. Nevertheless you have to type
that option altough the only permitted value is 'avr*'

2) It is a library for my 'target', not for my 'host'.  The hosting machine
typically is a Linux or Windows PC.  That's why I stumbled over this issue in
the first place. I naivly tried "./configure --target=avr" as for binutils and
gcc and it failed.  (I can vaguely imagine a logic why it is called host, but
that's very counterintuitive!)

3) I had a third reason when I opened the issue but I don't remember
anymore...

I propose to accept --target= as an equivalent to --host in the first step,
correct the build instructions and then to deprecate --host as a target
indicator (it might still be useful for an alternative name of --build in case
config.guess fails to correctly detect the hosting machine)

    Rolf




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?35483>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/


_______________________________________________
AVR-libc-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
Reply | Threaded
Open this post in threaded view
|

[bug #35483] ./configure does not accept --target

Kevin Cuzner-2
Update of bug #35483 (project avr-libc):

                Severity:              3 - Normal => 1 - Wish              

    _______________________________________________________

Follow-up Comment #1:

All that stuff still originates from Ted Roth's initial work on the
autoconf setup (back in 2004, the first revision appeared on branch
"autoconf-branch", it's r498 now after the migration to SVN).
Frankly, I've got no idea why he required this scheme, but I'm pretty
sure he's got a reason by that time. ;-)

If someone could come up with a better implementation that produces
similar results, I'm all ears.


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?35483>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
AVR-libc-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
Reply | Threaded
Open this post in threaded view
|

[bug #35483] ./configure does not accept --target

Kevin Cuzner-2
Update of bug #35483 (project avr-libc):

                Priority:              5 - Normal => 1 - Later              


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?35483>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
AVR-libc-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
Reply | Threaded
Open this post in threaded view
|

[bug #35483] ./configure does not accept --target

Kevin Cuzner-2
Follow-up Comment #2, bug #35483 (project avr-libc):

--host specifies the platform that runs the software, thus --target=avr would
be confusing.

--host is common practice.  For example, if you cross-build libraries like GSL
(so that they run on a platform fifferent to the build platform), you specify
that by means of --host.


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?35483>

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.nongnu.org/


_______________________________________________
AVR-libc-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
Reply | Threaded
Open this post in threaded view
|

[bug #35483] ./configure does not accept --target

Kevin Cuzner-2
Follow-up Comment #3, bug #35483 (project avr-libc):

this bug is invalid and should be closed.  avr-libc is behaving correctly.

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

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?35483>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/


_______________________________________________
AVR-libc-dev mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
Reply | Threaded
Open this post in threaded view
|

[bug #35483] ./configure does not accept --target

Kevin Cuzner-2
Follow-up Comment #4, bug #35483 (project avr-libc):

[comment #3 comment #3:]
> this bug is invalid and should be closed.  avr-libc is behaving correctly.

Sorry, I tend to disagree: it is NOT behaving correctly.

> 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:

  --target=avr --build=x86_64-pc-linux-gnu --host=x86_64-pc-windows

or something. After all, the AVR is not executing the toolchain. It is
executing the code which is generated by the toolchain.

The semantic of --host=avr is to build a toolchain which is running on the
AVR. I doubt that anybody is really trying to do such a thing...

Every other tool in the world specifies it this way.

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


    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/bugs/?35483>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/


Reply | Threaded
Open this post in threaded view
|

[bug #35483] ./configure does not accept --target

Kevin Cuzner-2
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/