Skip to content

llvmPackages: change default to 3.9 #20461

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

Closed
wants to merge 1 commit into from

Conversation

rasendubi
Copy link
Member

Motivation for this change

See #19195.

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
    • Linux
  • 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.

Note that llvmPackages and llvmPackagesSelf were out of sync—I'm not sure if that was intended. (If that was, we should add a comment explaining this.)

That's probably a mass rebuild (at least for darwin), so opening against staging.

Sorry, something went wrong.

@copumpkin
Copy link
Member

Can you actually make this conditional on darwin and leave it alone (i.e., still at 3.7) on that platform? I'm trying to upgrade to 3.8 right now but there are issues we've been encountering with c++ compatibility and so on.

@rasendubi
Copy link
Member Author

@copumpkin done

@copumpkin
Copy link
Member

Thanks! I assume you've built whatever depends on it on Linux? I vaguely remember mesa and things downstream from it using llvm.

The issues with LLVM have mostly been around certain changes in libc++ that happened in 3.8, and made several packages stop compiling with it. Those issues are obviously exacerbated by Darwin using LLVM to build everything, but I imagine you might find similar issues on whichever packages build with it on Linux too.

@rasendubi
Copy link
Member Author

mesa doesn't seem to depend on llvm—Nix took one from the cache.

*** Downloading ‘https://cache.nixos.org/nar/1y90k9rq1mjxd6b594gshzxnizgvmq26zjdfjkxvfc53vixw63g1.nar.xz’ to ‘/nix/store/8rkvqz2x0hr23313qk2wi1ap7nffzj1k-mesa-13.0.1’...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1160  100  1160    0     0    780      0  0:00:01  0:00:01 --:--:--   783

/nix/store/8rkvqz2x0hr23313qk2wi1ap7nffzj1k-mesa-13.0.1

@copumpkin
Copy link
Member

Hmm, I must be misremembering. Either way, nox-review should be able to check stuff for you 😄

@rasendubi
Copy link
Member Author

Running it now.

btw, it always takes long on ==> We're in a git repo, trying to fetch it moment. Is that ok?

@rasendubi
Copy link
Member Author

error: while querying the derivation named ‘clang-wrapper-wrapper-3.9.0’:
while evaluating the attribute ‘buildCommand’ of the derivation ‘clang-wrapper-wrapper-3.9.0’ at /home/rasen/.nox/nixpkgs/pkgs/build-support/cc-wrapper/default.nix:40:3:
attribute ‘gcc’ missing, at /home/rasen/.nox/nixpkgs/pkgs/build-support/cc-wrapper/default.nix:194:38

@copumpkin
Copy link
Member

Yay for nox-review! No idea what's wrong, but at least it found the problem before it bit us 😄

@shlevy
Copy link
Member

shlevy commented Nov 17, 2016

@copumpkin what are the issues with 3.8 on darwin?

@copumpkin
Copy link
Member

@shlevy http://hydra.nixos.org/eval/1304050?compare=staging is somewhat informative for figuring that out, although I wish we could only look for red crosses

@copumpkin
Copy link
Member

@shlevy there were some bdb incompatibilities that @LnL7 fixed here (and in similar patches for other versions): https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/db/clang-5.3.patch

@LnL7
Copy link
Member

LnL7 commented Nov 17, 2016

I also discovered yesterday that removing the --enable-dbm flag will also fix one of the issues, that probably better then patching it.

@copumpkin
Copy link
Member

@LnL7 don't we want dbm-like stuff though?

@LnL7
Copy link
Member

LnL7 commented Nov 17, 2016

It's some sort of legacy interface apparently, so hopefully not. If something needs it I would assume that the current patch also breaks it.

@rasendubi
Copy link
Member Author

Could someone help me find clang-wrapper-wrapper? I've build all of llvmPackages fine.

@gebner
Copy link
Member

gebner commented Nov 17, 2016

mesa doesn't seem to depend on llvm—Nix took one from the cache.

Mesa certainly depends on LLVM, but we have already been using 3.9 in mesa for a long time:

llvmPackages = llvmPackages_39;

@vcunat
Copy link
Member

vcunat commented Nov 19, 2016

llvmPackagesSelf.llvm won't build for me if switched to 3.9:

/tmp/nix-build-llvm-3.9.0.drv-0/llvm/projects/compiler-rt/lib/tsan/dd/dd_interceptors.cc:226:20: error: redefinition of 'realpath'
INTERCEPTOR(char*, realpath, const char *path, char *resolved_path) {
                   ^
/nix/store/7lmqs27llkmmzd8lczjrhq805w48zp15-glibc-2.24-dev/include/bits/stdlib.h:37:8: note: previous definition is here
__NTH (realpath (const char *__restrict __name, char *__restrict __resolved))

vcunat added a commit that referenced this pull request Nov 19, 2016
It seems not to be any mass rebuild at all.
@vcunat
Copy link
Member

vcunat commented Nov 19, 2016

I switched llvmPackages at least, directly in master.

vcunat added a commit that referenced this pull request Nov 19, 2016
@vrthra vrthra added the 2.status: merge conflict This PR has merge conflicts with the target branch label Feb 11, 2017
@Mic92
Copy link
Member

Mic92 commented May 23, 2017

obsolete

@Mic92 Mic92 closed this May 23, 2017
@rrbutani rrbutani added the 6.topic: llvm/clang Issues related to llvmPackages, clangStdenv and related label May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.status: merge conflict This PR has merge conflicts with the target branch 6.topic: llvm/clang Issues related to llvmPackages, clangStdenv and related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants