Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
build: use arm64 as DESTCPU for aarch64 #22548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
build: use arm64 as DESTCPU for aarch64 #22548
Changes from 1 commit
fc228311dedf3fFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
On a `aarch64` system I can run the complete build with tests without specifying the Makefile variable `DESTCPU`. But when running the `tar-headers` target `DESTCPU` is passed to configure: ```shell $(PYTHON) ./configure \ --prefix=/ \ --dest-cpu=$(DESTCPU) \ ... ``` The value of `DESTCPU` in this case will be 'aarch64' which will cause configure to fail: ```shell configure: error: option --dest-cpu: invalid choice: 'aarch64' (choose from 'arm', 'arm64', 'ia32', 'mips', 'mipsel', 'mips64el', 'ppc', 'ppc64', 'x32', 'x64', 'x86', 'x86_64', 's390', 's390x') ``` In the configure script there is a matching of `__aarch64__` to `arm64`: ```shell $ python -c 'from configure import host_arch_cc; print host_arch_cc()' arm64 ``` In our case it would be nice to have consitent behaviour for both of these cases on `aarch64`. This commit changes `DESTCPU` to `arm64` to be consistent with the configure script. `DESTCPU` is used in `$(TARBALL)-headers` and in `$(BINARYTAR)` but I'm not sure about the implications of making the change purposed and hope others might chime in and provide some guidance.Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing