configure --target=arm-unknown-linux-gnueabihf,arm-unknown-linux-gnueabi ignores the arm-unknown-linux-gnueabi target
#32176
Labels
C-bug
Category: This is a bug.
Comments
|
Weird... we probably have some crazy logic in the configure script which doesn't account for prefixes or something like that. |
|
Seems that this is still an issue. However, I don't know whether this actually causes problems with rustbuild. Perhaps @alexcrichton could comment? |
|
Unfortunately not much more than before, probably still the same crazy ./configure logic |
bors
added a commit
that referenced
this issue
Aug 28, 2017
…crum rustbuild: Rewrite the configure script in Python This commit rewrites our ancient `./configure` script from shell into Python. The impetus for this change is to remove `config.mk` which is just a vestige of the old makefile build system at this point. Instead all configuration is now solely done through `config.toml`. The python script allows us to more flexibly program (aka we can use loops easily) and create a `config.toml` which is based off `config.toml.example`. This way we can preserve comments and munge various values as we see fit. It is intended that the configure script here is a drop-in replacement for the previous configure script, no functional change is intended. Also note that the rationale for this is also because our build system requires Python, so having a python script a bit earlier shouldn't cause too many problems. Closes #40730 Closes #43295 Closes #42255 Closes #38058 Closes #32176
bors
added a commit
that referenced
this issue
Aug 28, 2017
…crum rustbuild: Rewrite the configure script in Python This commit rewrites our ancient `./configure` script from shell into Python. The impetus for this change is to remove `config.mk` which is just a vestige of the old makefile build system at this point. Instead all configuration is now solely done through `config.toml`. The python script allows us to more flexibly program (aka we can use loops easily) and create a `config.toml` which is based off `config.toml.example`. This way we can preserve comments and munge various values as we see fit. It is intended that the configure script here is a drop-in replacement for the previous configure script, no functional change is intended. Also note that the rationale for this is also because our build system requires Python, so having a python script a bit earlier shouldn't cause too many problems. Closes #40730 Closes #43295 Closes #42255 Closes #38058 Closes #32176
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
STR
Meta
cc @alexcrichton
The text was updated successfully, but these errors were encountered: