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

go_1_17: enable on x86_64-darwin #144644

Merged
merged 1 commit into from Nov 6, 2021
Merged

go_1_17: enable on x86_64-darwin #144644

merged 1 commit into from Nov 6, 2021

Conversation

r-burns
Copy link
Contributor

@r-burns r-burns commented Nov 4, 2021

Apparently this does not depend on stdenv's macOS SDK at all,
and carries around its own go-specific toolchain. So this works
fine as-is and doesn't need any changes in Nixpkgs to support a
10.13 deployment target.

Motivation for this change

Noticed in #144588 (comment)

If this is valid, it would be nice to have for 21.11 (linking #144627 for visibility)

Things done
  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 21.11 Release Notes (or backporting 21.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

@bobrik
Copy link
Contributor

bobrik commented Nov 4, 2021

Can we also update go = go_1_16 to 1.17 in all-packages.nix then?

@r-burns
Copy link
Contributor Author

r-burns commented Nov 4, 2021

Yes, I think so. Happy to do so here or in a separate PR, whatever's preferred.

@bobrik
Copy link
Contributor

bobrik commented Nov 4, 2021

There's also this:

  # go_1_17 has go module changes which may not be portable
  # across different go versions and/or platforms,
  # it also requires >=10.13 stdenv on darwin which
  # is not currently available for x86_64-darwin
  #
  # do not uncomment this without approval from the go CODEOWNERS
  #buildGo117Module = callPackage ../development/go-modules/generic {
  #  go = buildPackages.go_1_17;
  #};

  buildGoModule = buildGo116Module;

Not sure if those non-portable go module changes is something that needs to be addressed.

@r-burns
Copy link
Contributor Author

r-burns commented Nov 4, 2021

AFAIK: the "non-portable module changes" part is the reason we can't just go buildGoModule = buildGo117Module immediately, but is independent from the 10.13 SDK concerns. So I think this PR should remove the SDK 10.13 remark from that comment but otherwise leave it untouched.

Copy link
Contributor

@thiagokokada thiagokokada left a comment

Choose a reason for hiding this comment

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

Result of nixpkgs-review pr 144644 run on x86_64-darwin 1

1 package built:
  • go_1_17

Apparently this does not depend on stdenv's macOS SDK at all,
and carries around its own go-specific toolchain. So this works
fine as-is and doesn't need any changes in Nixpkgs to support a
10.13 deployment target.
@risicle
Copy link
Contributor

risicle commented Nov 6, 2021

Are we waiting on something here?

@thiagokokada
Copy link
Contributor

Are we waiting on something here?

Maybe someone that knows more about Go to merge?

@r-burns
Copy link
Contributor Author

r-burns commented Nov 6, 2021

I was hoping for an ACK from one of the Go codeowners, but it looks like everyone is ok with this. And this is a small change so it's easy to revert if needed.

@domenkozar domenkozar merged commit 2606cb0 into NixOS:master Nov 6, 2021
@r-burns r-burns deleted the go branch November 6, 2021 19:50
@Ma27
Copy link
Member

Ma27 commented Nov 6, 2021

AFAIK: the "non-portable module changes" part is the reason we can't just go buildGoModule = buildGo117Module immediately, but is independent from the 10.13 SDK concerns. So I think this PR should remove the SDK 10.13 remark from that comment but otherwise leave it untouched.

That doesn't mean we can enable buildGo117Module though, right? :)
Anyway, I'll take care of that in the Grafana update PR.

@nixos-discourse
Copy link

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/missing-go-1-17-on-x86-64-darwin/15032/3

@r-burns r-burns mentioned this pull request May 14, 2022
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

9 participants