| 9 May 2026 |
K900 | No but I wonder if it's possible we're firing off a build before all the outputs are fully done and committed | 17:18:32 |
emily | oh, yeah | 17:18:43 |
emily | the race condition seems plausible since we do get multiple builds happening on Hydra, I did mention that in an earlier comment | 17:18:57 |
emily | but I guess forgot :) | 17:19:01 |
Randy Eckenrode | This reproduces from master.
$ nix shell github:NixOS/nixpkgs#darwin.dyld --command dsc_extractor
$ nix develop github:NixOS/nixpkgs#darwgithub:NixOS/nixpkgs#darwin.dyld —command dsc_extractor/nixpkgs#darwin.dyld.out)
$ nix shell --option substitute false github:NixOS/nixpkgs#darwin.dyld —command dsc_extractor
| 17:24:11 |
Randy Eckenrode | * This reproduces from master.
$ nix shell github:NixOS/nixpkgs#darwin.dyld --command dsc_extractor
$ nix store delete $(nix eval --raw github:NixOS/nixpkgs#darwin.dyld.out)
$ nix develop github:NixOS/nixpkgs#darwgithub:NixOS/nixpkgs#darwin.dyld —command dsc_extractor/nixpkgs#darwin.dyld.out)
$ nix shell --option substitute false github:NixOS/nixpkgs#darwin.dyld —command dsc_extractor
| 17:24:40 |
Randy Eckenrode | * This reproduces from master.
$ nix shell github:NixOS/nixpkgs#darwin.dyld --command dsc_extractor
$ nix store delete $(nix eval --raw github:NixOS/nixpkgs#darwin.dyld.out)
$ nix develop github:NixOS/nixpkgs#darwgithub:NixOS/nixpkgs#darwin.dyld —command dsc_extractor
$ nix shell --option substitute false github:NixOS/nixpkgs#darwin.dyld —command dsc_extractor
| 17:25:00 |
emily | yeah, I mean it's unsurprising that this does break things, it's the same as --rebuild | 17:25:03 |
emily | what surprises me is that there's at least one piece of evidence that it's what's causing the persistent Hydra issues | 17:25:14 |
Randy Eckenrode | * This reproduces from master.
$ nix shell github:NixOS/nixpkgs#darwin.dyld --command dsc_extractor
$ nix store delete $(nix eval --raw github:NixOS/nixpkgs#darwin.dyld.out)
$ nix develop github:NixOS/nixpkgs#darwgithub:NixOS/nixpkgs#darwin.dyld --command dsc_extractor
$ nix shell --option substitute false github:NixOS/nixpkgs#darwin.dyld --command dsc_extractor
| 17:25:18 |
emily | given ^, it didn't seem like there would be common cases where Hydra would be building only some outputs | 17:25:32 |
Randy Eckenrode | * This reproduces from master.
$ nix shell github:NixOS/nixpkgs?ref=3ac379d7981fbe8bd4d22c25f9df4b7e56f53f71#darwin.dyld --command dsc_extractor
$ nix store delete $(nix eval --raw github:NixOS/nixpkgs?ref=3ac379d7981fbe8bd4d22c25f9df4b7e56f53f71#darwin.dyld.out)
$ nix develop github:NixOS/nixpkgs#darwgithub:NixOS/nixpkgs?ref=3ac379d7981fbe8bd4d22c25f9df4b7e56f53f71#darwin.dyld --command dsc_extractor
$ nix shell --option substitute false github:NixOS/nixpkgs?ref=3ac379d7981fbe8bd4d22c25f9df4b7e56f53f71#darwin.dyld --command dsc_extractor
| 17:28:33 |
Randy Eckenrode | * This reproduces from master.
$ nix shell github:NixOS/nixpkgs?ref=3ac379d7981fbe8bd4d22c25f9df4b7e56f53f71#darwin.dyld --command dsc_extractor
$ nix store delete $(nix eval --raw github:NixOS/nixpkgs?ref=3ac379d7981fbe8bd4d22c25f9df4b7e56f53f71#darwin.dyld.out)
$ nix develop github:NixOS/nixpkgs#darwgithub:NixOS/nixpkgs?ref=3ac379d7981fbe8bd4d22c25f9df4b7e56f53f71#darwin.dyld --command dsc_extractor
$ nix shell --option substitute false github:NixOS/nixpkgs?ref=3ac379d7981fbe8bd4d22c25f9df4b7e56f53f71#darwin.dyld --command dsc_extractor
| 17:28:44 |
Randy Eckenrode | https://github.com/NixOS/nixpkgs/issues/507531#issuecomment-4392137594 | 17:31:50 |
Randy Eckenrode | I guess I’m glad it’s not my fault for relying on ld64’s native code signing instead of using postLinkSignHook with ld-wrapper. 😅 | 17:34:28 |
emily | https://github.com/NixOS/infra/pull/1030 may help mitigate our long national nightmare | 20:36:07 |
| tnias joined the room. | 21:12:21 |
tnias | I'm trying to figure out why oxigraph is broken for aarch64-darwin.
The build fails in the check phase, when it tries to execute the cli tool.
If I just build it and then try to run the binary I get Trace/BPT trap: 5.
And I can't seem to start it in a debugger.
Any ideas what is happening here? Is this some dylib magic?
Note: I only have access to a macos system in form of a normal user account on darwin-build-box.nix-community.org. I believe I can't install tools like otool.
% nix develop nixpkgs\#oxigraph
...
tnias@darwin01 ~/nixpkgs (git)-[master] % nix develop nixpkgs\#oxigraph
bash-5.3$ unpackPhase
unpacking source archive /nix/store/jld4vdd2sx5g52af4xgcm6nyz9q00qq3-source
source root is source
Executing cargoSetupPostUnpackHook
Finished cargoSetupPostUnpackHook
bash-5.3$ cd source/
bash-5.3$ cargoBuildHook
Executing cargoBuildHook
~/nixpkgs/source/cli ~/nixpkgs/source
cargoBuildHook flags: -j 2 --target aarch64-apple-darwin --offline --profile release --no-default-features --features=rustls-webpki\,geosparql\,rdf-12
Compiling proc-macro2 v1.0.106
Compiling unicode-ident v1.0.24
...
Compiling siphasher v1.0.2
Compiling spargeo v0.5.4 (/Users/tnias/nixpkgs/source/lib/spargeo)
warning: oxrocksdb-sys@0.5.7: Inherited flag "-fno-omit-frame-pointer" is not supported by the currently used CC
warning: oxrocksdb-sys@0.5.7: Inherited flag "-fno-omit-frame-pointer" is not supported by the currently used CC
warning: oxrocksdb-sys@0.5.7: Warning: supplying the --target arm64-apple-macosx != arm64-apple-darwin argument to a nix-wrapped compiler may not work correctly - cc-wrapper is currently not designed with multi-target compilers in mind. You may want to use an un-wrapped compiler instead.
...
warning: oxrocksdb-sys@0.5.7: Warning: supplying the --target arm64-apple-macosx != arm64-apple-darwin argument to a nix-wrapped compiler may not work correctly - cc-wrapper is currently not designed with multi-target compilers in mind. You may want to use an un-wrapped compiler instead.
Compiling oxigraph v0.5.7 (/Users/tnias/nixpkgs/source/lib/oxigraph)
Finished `release` profile [optimized] target(s) in 5m 44s
~/nixpkgs/source
Executing cargoInstallPostBuildHook
Finished cargoInstallPostBuildHook
Finished cargoBuildHook
bash-5.3$ ./target/aarch64-apple-darwin/release/oxigraph load --location db --format ttl
Trace/BPT trap: 5 ./target/aarch64-apple-darwin/release/oxigraph load --location db --format ttl
bash-5.3$ rizin ./target/aarch64-apple-darwin/release/oxigraph
WARNING: bin_file_strings: search interval size (0xc44000) exeeds max region size (0xa00000), skipping it.
WARNING: bin_file_strings: search interval size (0xc44000) exeeds max region size (0xa00000), skipping it.
-- Toggle between disasm and graph with the space key
[0x10011b178]> il
library
------------------------------------------------------------------------------------
/usr/lib/libc++.1.dylib
/nix/store/xvmhkpvfvmy4sfdkqwg9inq3qkpnx81b-libiconv-109.100.2/lib/libiconv.2.dylib
/usr/lib/libSystem.B.dylib
[0x10011b178]>
bash-5.3$ ls -l /nix/store/xvmhkpvfvmy4sfdkqwg9inq3qkpnx81b-libiconv-109.100.2/lib/libiconv.2.dylib
-r-xr-xr-x 2 root nixbld 92352 Jan 1 1970 /nix/store/xvmhkpvfvmy4sfdkqwg9inq3qkpnx81b-libiconv-109.100.2/lib/libiconv.2.dylib
bash-5.3$ lldb ./target/aarch64-apple-darwin/release/oxigraph
(lldb) target create "./target/aarch64-apple-darwin/release/oxigraph"
Current executable set to '/Users/tnias/nixpkgs/source/target/aarch64-apple-darwin/release/oxigraph' (arm64).
(lldb) process launch
error: executable doesn't exist: '(empty)'
(lldb) ^D
bash-5.3$ gdb ./target/aarch64-apple-darwin/release/oxigraph
GNU gdb (GDB) 17.1
Copyright (C) 2025 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=aarch64-apple-darwin25.3.0 --target=x86_64-apple-darwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./target/aarch64-apple-darwin/release/oxigraph...
warning: Could not open OSO archive file "/Users/tnias/nixpkgs/source/target/aarch64-apple-darwin/release/deps/rustcit1J0d/libring-4b86aaa874f2b57b.rlib"
(No debugging symbols found in ./target/aarch64-apple-darwin/release/oxigraph)
(gdb) r
Don't know how to run. Try "help target".
(gdb) quit
bash-5.3$
| 23:41:33 |
emily | we have otool etc. in Nixpkgs, as part of the LLVM bintools | 23:44:43 |
Randy Eckenrode | nix shell nixpkgs#darwin.binutils --command otool | 23:47:58 |
tnias | It looks like otool can properly resolve all dylibs.
bash-5.3$ otool -L ./target/aarch64-apple-darwin/release/oxigraph
./target/aarch64-apple-darwin/release/oxigraph:
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 2000.63.0)
/nix/store/xvmhkpvfvmy4sfdkqwg9inq3qkpnx81b-libiconv-109.100.2/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1345.100.2)
bash-5.3$
| 23:52:04 |
| 10 May 2026 |
emily | is rcodesign happy with the code signature? | 00:03:15 |
tnias | I used the rcodesign from nixpkgs and it seems unhappy.
[nix-shell:~/nixpkgs/source]$ rcodesign verify ./target/aarch64-apple-darwin/release/oxigraph
(the verify command is known to be buggy and gives misleading results; we highly recommend using Apple's tooling until this message is removed)
no cryptographic signature present
Error: problems reported during verification
| 00:06:31 |
emily | hmm I don't know if it can check ad hoc codesignatures (and I'm guessing you don't have /usr/bin/codesign) | 00:12:53 |
tnias | Ohh, I have that. And it is not unhappy?
tnias@darwin01 ~/nixpkgs (git)-[master] % /usr/bin/codesign -v source/target/aarch64-apple-darwin/release/oxigraph
tnias@darwin01 ~/nixpkgs (git)-[master] % echo $?
0
| 00:25:40 |
emily | yeah, so something else | 00:30:18 |
emily | are you sure your LLDB syntax is right? I'm not fluent in LLDB but error: executable doesn't exist: '(empty)' seems suspicious | 00:30:36 |
tnias | process launch works on linux. I got it from the official lldb tutorial (https://lldb.llvm.org/use/tutorial.html)
Plus, gdb did not work either.
I only tried lldb, because I thought it is the debugger used by apple.
| 00:34:57 |
emily | does log stream show anything weird come up when you try to run the binary? | 00:36:48 |
tnias | tnias@darwin01 ~/nixpkgs (git)-[master] % /usr/bin/log stream
log: Must be admin to run 'stream' command
| 00:40:54 |