staging-next 2023-08-11 #248496
Merged
staging-next 2023-08-11 #248496
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
darwin-stdenv: revert `NIX_CC_NO_RESPONSE_FILE` logic
Fix implicit declarations of `memset` and `open/closedir` resulting in incorrect feature detection and conflicts with libc headers.
cc-wrapper: use a temporary file for reponse file
Signed-off-by: Henri Rosten <[email protected]>
...into staging
...into staging
codesign_allocate: use absolute path
The highlight is loongarch64 support. Changes: https://gmplib.org/gmp6.3
3.2 LTS ran out of mainstream support in 2021/12 and we should probably stay on the latest LTS release, that receives mainstream support.
Not useful any longer and started failing to build with django 4.
A few failing tests, but disabling individual ones is not straight forward.
Previously propagated by django_3, but not anymore by django_4.
Uses API functions deprecated in Django 3.0 and removed in 4.0.
One failing test with Django 4.2, that I reported upstream. Also migrate tests to pytest, so I can disable the failing test easily.
by backporting patches, that have not yet made it into a new release. Move django into buildInputs, because we require consumers to bring their own django version anyway. Migrate tests to pytest, because they work very well and are easier to maintain.
and point people to the guardian2 fork.
[staging-next] treewide: pin packages that don't build with new protobuf to old protobuf
treewide: more protobuf downgrades
Protobuf 3.22 supports python 3.11 already by including the same patch.
[staging-next] More misc fixes
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/call-for-help-build-failure-tensorflow/31945/1 |
|
I ran I think I have a fix. It’s building right now. It accommodates 6f2b3ba without reverting it (since it’s needed by Darwin for clang 16). |
The Swift compiler derivation modifies the clang wrapper to use `exec -a "$0"` to allow it to use the same binary for both `clang` and `clang++`. The sed script it uses to do this fails after the cc-wrapper changes in 6f2b3ba were merged. This is fixed by updating `makeClangWrapper` to work with the cc-wrapper changes by having Bash invoke a simple script that uses `exec -a "$0"` to set the required name for clang. This fixes the staging-next build failures with Swift on Darwin and Linux. #248496 (comment)
12 tasks
...into staging-next
This was referenced Aug 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Helpful links
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
https://hydra.nixos.org/job/nixos/staging-next-small/tested
https://hydra.nixos.org/jobset/nixpkgs/staging-next
https://hydra.nixos.org/jobset/nixos/staging-next-small
Mass breakages
(will be edited based on progress)
swift(lib)tensorflow