!UNVBThoJtlIiVwiDjU:nixos.org

Staging

353 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.11 | Review Reports: https://malob.github.io/nix-review-tools-reports/115 Servers

Load older messages


SenderMessageTime
7 Mar 2026
@dramforever:matrix.orgdramforeverso it's at least fragile somehow?11:54:18
@yuka:yuka.devYureka (she/her)https://github.com/openMathLib/openBLAS/commit/05fc88180c42eae7588fac4bd59c3b86ffefbc2312:10:18
@yuka:yuka.devYureka (she/her)reverting this fixes the build on both Ampere and M1 Pro12:10:33
@yuka:yuka.devYureka (she/her)https://github.com/NixOS/nixpkgs/pull/49753812:15:41
@k900:0upti.meK900Can't you just makeflags BUILD_BFLOAT16=0?12:21:56
@dramforever:matrix.orgdramforever

oh come on

  postPatch = ''
    # cc1: error: invalid feature modifier 'sve2' in '-march=armv8.5-a+sve+sve2+bf16'
    substituteInPlace Makefile.arm64 --replace-fail "+sve2+bf16" ""
  '';
12:23:04
@dramforever:matrix.orgdramforevercome on12:23:07
@dramforever:matrix.orgdramforeverturns out we played ourselves12:23:53
@dramforever:matrix.orgdramforevercommented on the pr12:28:34
@yuka:yuka.devYureka (she/her)wait what?12:36:24
@yuka:yuka.devYureka (she/her) wouldn't replace-fail fail if it didn't replace anything? 12:36:34
@yuka:yuka.devYureka (she/her)or does it only replace the first occurance12:38:36
@yuka:yuka.devYureka (she/her)No12:41:02
@yuka:yuka.devYureka (she/her)Oh I understand now12:42:26
@yuka:yuka.devYureka (she/her)We shouldn't be replacing/removing this flag anymore12:42:37
@yuka:yuka.devYureka (she/her)And when keeping it, the new version builds12:42:46
@dramforever:matrix.orgdramforevernow the question is how did this ever build on aarch64-linux12:48:07
@yuka:yuka.devYureka (she/her)maybe it didn't and someone misclicked?13:09:59
@9hp71n:matrix.orgghpzin it doesn't fix opencv thing right ? 13:16:09
@dramforever:matrix.orgdramforeverwhat's the opencv thing13:16:58
@yuka:yuka.devYureka (she/her) https://github.com/NixOS/nixpkgs/issues/495748
https://github.com/NixOS/nixpkgs/issues/495726
are now also happening on staging-next (I previously reported them on staging)
13:22:37
@dramforever:matrix.orgdramforeverget these googlers IWYU13:30:48
@yuka:yuka.devYureka (she/her) These ones are new: protobufc, onnxruntime
https://github.com/NixOS/nixpkgs/issues/497555
https://github.com/NixOS/nixpkgs/issues/497556
13:33:15
@9hp71n:matrix.orgghpzin There is some separate openblas build pulled by opencv that is broken on x86_64-linux:
...
/nix/store/rfp8lhk4dl9syfn64rwb3h3c73426p08-binutils-2.44/bin/ld: /build/ccz2kZvK.o: in function `main':
linktest.c:(.text.startup+0x3142): undefined reference to `openblas_set_threads_callback_function'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:211: ../libopenblas-r0.3.31.so] Error 1
make[1]: Leaving directory '/build/source/exports'
make: *** [Makefile:149: shared] Error 2
but I guess it is a different issue from aarch64-linux one.
13:35:11
@dramforever:matrix.orgdramforeverdifferent issue13:35:44
@9hp71n:matrix.orgghpzin There is some separate openblas build pulled by opencv that is broken on x86_64-linux:
...
/nix/store/rfp8lhk4dl9syfn64rwb3h3c73426p08-binutils-2.44/bin/ld: /build/ccz2kZvK.o: in function `main':
linktest.c:(.text.startup+0x3142): undefined reference to `openblas_set_threads_callback_function'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:211: ../libopenblas-r0.3.31.so] Error 1
make[1]: Leaving directory '/build/source/exports'
make: *** [Makefile:149: shared] Error 2
but I guess it is a different issue from aarch64-linux one.
---
Upstream issue: https://github.com/OpenMathLib/OpenBLAS/issues/5607
Probably need this: https://github.com/OpenMathLib/OpenBLAS/commit/14594773a0c06b1fb40208dcdbd3aad4c39d845d
13:51:01
@matthewcroughan:defenestrate.itmatthewcroughanAny objections to merging https://github.com/NixOS/nixpkgs/pull/49735816:09:15
@matthewcroughan:defenestrate.itmatthewcroughanSeems like it has been done before, and merged then, and seems to be a recurring theme16:09:25
@matthewcroughan:defenestrate.itmatthewcroughanMaybe we should never ever use the "latest" in this derivation, and always pin it16:10:28
@matthewcroughan:defenestrate.itmatthewcroughanthe fact that it was ever allowed to be pointing to latest, seems to be the issue, no?16:10:40

There are no newer messages yet.


Back to Room ListRoom Version: 6