Skip to content
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

Revert "gcc, binutils: Get rid of 32-bit ARM configure flag exception" #33641

Merged
merged 1 commit into from Jan 9, 2018
Merged

Revert "gcc, binutils: Get rid of 32-bit ARM configure flag exception" #33641

merged 1 commit into from Jan 9, 2018

Conversation

dhess
Copy link
Contributor

@dhess dhess commented Jan 9, 2018

0f5c804 broke native armv7l-linux builds. @Ericson2314 understandably has his hands full, so in the meantime, I would like to un-wedge armv7l-linux until he has a chance to revisit this. It is currently not possible to build practically anything for that platform on master or on any of the unstable channels.

This reversion does not affect behavior on other platforms or for armv7l-linux cross-compiling, as far as I can tell.

I tested this on master by successfully building a Linux kernel and its dependencies.

Motivation for this change

Fixes #33403

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

This commit breaks native armv7l-linux builds. Revert it until it can
be root-caused. This reversion does not affect other platforms or
cross-compiling.

This reverts commit 0f5c804.
@orivej orivej merged commit 7a891eb into NixOS:master Jan 9, 2018
@dhess dhess deleted the gcc-armv7l-fix branch January 9, 2018 12:27
@dhess
Copy link
Contributor Author

dhess commented Jan 9, 2018

Thank you!

@Ericson2314
Copy link
Member

Yeah this is totally justified. Sorry I didn't do it myself :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants