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

chromium: fix aarch64 build #74015

Merged
merged 1 commit into from Nov 26, 2019
Merged

Conversation

thefloweringash
Copy link
Member

The skia patch no longer applies, and is no longer necessary.

The current version of chromium doesn't build with gcc. This has been
fixed upstream[1] and could be backported, but switching aarch64 to
clang/llvm and making the build the same on all platforms is simpler.

[1] https://chromium.googlesource.com/chromium/src/+/9662ec844017690d5fd56bf0f05ef6a540dd29c1

Motivation for this change
Things done
  • 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 nix-review --run "nix-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.
Notify maintainers

cc @

@thefloweringash
Copy link
Member Author

This requires a libjack2 to build, which was fixed in #73779 and is currently in staging.

@flokli
Copy link
Contributor

flokli commented Nov 25, 2019

Can you fix the merge conflict, and rebase on top of staging, so this should build?

@bendlas
Copy link
Contributor

bendlas commented Nov 25, 2019

fixed commit is here: bendlas@c829108

I held off merging it, because of the staging isse. should probably be merged, because build is already broken

@thefloweringash thefloweringash changed the base branch from master to staging November 25, 2019 14:36
The skia patch no longer applies, and is no longer necessary.

The current version of chromium doesn't build with gcc. This has been
fixed upstream[1] and could be backported, but switching aarch64 to
clang/llvm and making the build the same on all platforms is simpler.

[1] https://chromium.googlesource.com/chromium/src/+/9662ec844017690d5fd56bf0f05ef6a540dd29c1
@bendlas
Copy link
Contributor

bendlas commented Nov 26, 2019

ofborg timing out on 3600 seconds is to be expected, but the log up to that looks normal (we should do something about the warnings, that recently popped up, at some point)

@bendlas bendlas merged commit 6ec5e74 into NixOS:staging Nov 26, 2019
@thefloweringash thefloweringash deleted the chromium-aarch64 branch November 26, 2019 00:26
@bendlas
Copy link
Contributor

bendlas commented Nov 26, 2019

Oh, I just realized, the PR was against staging. That wouldn't have been necessary, I think, since chromium doesn't have any downstream. Or is this an aarch64-specific thing?

Let's pick this into stable, on next staging merge.

@thefloweringash
Copy link
Member Author

That wouldn't have been necessary, I think, since chromium doesn't have any downstream. Or is this an aarch64-specific thing?

I went from the recommendation earlier in the thread. There's no real advantage in putting it onto master before staging merges since it depends on the libjack2 fixes in staging.

@ivan
Copy link
Member

ivan commented Dec 15, 2019

@thefloweringash if you use chromium on aarch64, could you please add yourself to the chromium maintainers, so that you are pinged and can test version bumps like #75516? I cannot build or test on aarch64.

thefloweringash added a commit to thefloweringash/nixpkgs that referenced this pull request Dec 15, 2019
I have an interest in making Chromium available on Aarch64. I'm adding
myself here on a recommendation from @ivan [1].

[1] NixOS#74015 (comment)
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