!UNVBThoJtlIiVwiDjU:nixos.org

Staging

317 Members
Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen109 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
18 Sep 2025
@ghpzin:envs.netghpzin Somebody disabled them for loongarch64 recently, and yes on top of gcc15 it fails on that test constantly. 07:51:35
@k900:0upti.meK900Also on 14.3.007:52:08
@k900:0upti.meK900Seemingly07:52:08
@ghpzin:envs.netghpzin* Somebody disabled them for loongarch64 recently https://github.com/NixOS/nixpkgs/pull/426840 and yes on top of gcc15 it fails on that test constantly.07:53:07
@ghpzin:envs.netghpzin I almost managed to build graphical iso with ~30 fixes of questionable quality.
But then mesa fails with something strange.
08:35:38
@k900:0upti.meK900Mesa?08:43:48
@k900:0upti.meK900That's interesting08:43:50
@k900:0upti.meK900Do you have a log08:43:57
@ghpzin:envs.netghpzin
FAILED: [code=1] src/nouveau/compiler/nak_bindings.rs
/nix/store/rm899xgm82kanr814dk8siwyghyxwphg-rust-bindgen-0.72.0/bin/bindgen ../src/nouveau/compiler/nak_bindings.h
/build/source/src/nouveau/winsys/./nouveau_bo.h:41:4: error: unknown type name 'atomic_uint_fast32_t'
Unable to generate bindings: clang diagnosed error: /build/source/src/nouveau/winsys/./nouveau_bo.h:41:4: error: unknown type name 'atomic_uint_fast32_t'
08:44:16
@ghpzin:envs.netghpzin
FAILED: [code=1] src/nouveau/compiler/nak_bindings.rs
/nix/store/rm899xgm82kanr814dk8siwyghyxwphg-rust-bindgen-0.72.0/bin/bindgen ../src/nouveau/compiler/nak_bindings.h
/build/source/src/nouveau/winsys/./nouveau_bo.h:41:4: error: unknown type name 'atomic_uint_fast32_t'
Unable to generate bindings: clang diagnosed error: /build/source/src/nouveau/winsys/./nouveau_bo.h:41:4: error: unknown type name 'atomic_uint_fast32_t'
https://gist.github.com/ghpzin/35e5fb891645e02e5b2873761c593722
08:47:31
@k900:0upti.meK900https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/nouveau/winsys/nouveau_bo.h?ref_type=heads#L808:47:54
@k900:0upti.meK900I wonder if GCC changed stuff around stdatomic.h08:49:32
@k900:0upti.meK900https://github.com/gcc-mirror/gcc/commits/releases/gcc-15/gcc/ginclude/stdatomic.h08:50:59
@k900:0upti.meK900Doesn't look like it at least08:51:03
@ghpzin:envs.netghpzinThere was an issue upstream with that exact error, but "solution" was seemingly to just juggle installed libraries on ubuntu: https://gitlab.freedesktop.org/mesa/mesa/-/issues/1186908:53:25
@k900:0upti.meK900Are you sure this is a GCC version thing then and not an LLVM version thing?08:55:37
@ghpzin:envs.netghpzinIf you mean staging related LLVM changes, then no, it fails on top of master too. Maybe one of the fixes in the chain somehow affects it. Will try to minimize reproducer on master later.09:01:38
@ghpzin:envs.netghpzin* If you mean staging related LLVM changes, then no, it fails on top of master too. Maybe one of the fixes in the gcc15 chain somehow affects it. Will try to minimize reproducer on master later.09:03:23
@emilazy:matrix.orgemilyit would be fun but probably next cycle is the safe move. though I worry about freeze10:01:55
@emilazy:matrix.orgemilyactually if we're that close to the ISO then this cycle might work10:02:51
@emilazy:matrix.orgemilyehh probably not10:03:39
@k900:0upti.meK900Please do not this cycle10:31:03
@emilazy:matrix.orgemilyyeah probably what I'll do is run GCC 15 builds while the cycle runs10:31:56
@emilazy:matrix.orgemilyso that it's relatively ready for the next one10:32:05
@ghpzin:envs.netghpzin https://github.com/ghpzin/nixpkgs/tree/mesa-gcc15
Same error on top of current master
It only has: gcc15 default and 5 fixes to get to mesa building: ncompress, cpio, expect, yasm, woff2
Both mesa and mesa.override { stdenv = pkgs.gcc15Stdenv } seem to build fine on master
10:32:26
@k900:0upti.meK900Exciting10:32:42

Show newer messages


Back to Room ListRoom Version: 6