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

relibc: build from source #95848

Merged
merged 1 commit into from Aug 21, 2020
Merged

Conversation

aaronjanse
Copy link
Member

Motivation for this change

For #93661. Building things from source is generally good. I could eventually bootstrap even further from source, but for now, this PR should be a good step forward.

This PR also makes it easier for Nix users to contribute to relibc source code.

P.S. @Ericson2314 I'm close to getting a relibc-based toolchain working for Linux, after which I'll make a PR to add linux to relibc's meta.platforms :-)

Things done

I tested this by building a full Redox VM from it.

  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • 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 nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

buildPackages.stdenv.cc.libc
"$out"
];
bootstrapCrossRust = stdenvNoCC.mkDerivation {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would normally be pedantic and say this should be stdenvNoCC.mkDerivation buildPackages.stdenvNoCC.mkDerivation (and then you could probably just use autoPatchelfHook too), but I think this is about to be replaced in the other PRs so I am not oo concerned :).

Feel free to open another PR if you think this might last more than a few days, though.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would normally be pedantic and say this should be stdenvNoCC.mkDerivation

I assume that's a typo, because it's stdenvNoCC.mkDerivation already?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry! I meant to write buildPackages.stdenvNoCC.mkDerivation

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

2 participants