| 16 Oct 2025 |
 Randy Eckenrode | https://github.com/getsentry/sentry-cli/blob/b6d72df9a9f69bd244fc605cc18c8bfd2fd31a56/apple-catalog-parsing/build.rs#L33 should be /usr/lib/swift/macosx. The linker will find it relative to the SDKROOT. | 17:56:06 |
| Randy Eckenrode | https://github.com/getsentry/sentry-cli/blob/b6d72df9a9f69bd244fc605cc18c8bfd2fd31a56/apple-catalog-parsing/build.rs#L39_L61 needs to be swift-build due to the way we package Swift and SwiftPM. It expects to find swift-<subcommand> in the same path as swift. | 17:57:30 |
| Randy Eckenrode | https://github.com/getsentry/sentry-cli/blob/b6d72df9a9f69bd244fc605cc18c8bfd2fd31a56/apple-catalog-parsing/build.rs#L91 could just readDEVELOPER_DIR from the environment if xcode-select fails. | 17:58:50 |
| Randy Eckenrode | * https://github.com/getsentry/sentry-cli/blob/b6d72df9a9f69bd244fc605cc18c8bfd2fd31a56/apple-catalog-parsing/build.rs#L91 could just read DEVELOPER_DIR from the environment if xcode-select fails. | 17:58:57 |
| Randy Eckenrode | Using build.rs to run a Swift build is certainly a choice, but those are the only things that leap out to me. | 18:00:03 |
 samasaur | In reply to @reckenrode:matrix.org
https://github.com/getsentry/sentry-cli/blob/b6d72df9a9f69bd244fc605cc18c8bfd2fd31a56/apple-catalog-parsing/build.rs#L39_L61 needs to be swift-build due to the way we package Swift and SwiftPM. It expects to find swift-<subcommand> in the same path as swift. FWIW I think this is not an issue if you add both swift and swiftpm | 18:14:08 |
| Randy Eckenrode | It’s been a while since I messed with the Swift stuff, but I’m pretty sure it fails due to swift-build not being in the right place. That’s why the hook is written to invoke swift-build. I could be wrong though. | 18:15:13 |
| Randy Eckenrode | This time failure is weird. It fails to detect sighandler_t then uses __sighandler_t instead even though its provided signal.h provides a definition of sighandler_t. | 18:19:25 |
| samasaur | In reply to @reckenrode:matrix.org
It’s been a while since I messed with the Swift stuff, but I’m pretty sure it fails due to swift-build not being in the right place. That’s why the hook is written to invoke swift-build. I could be wrong though. I am basing my claim off the fact that I got past that stage of the build.rs file without changing it to swift-build | 18:23:24 |
| samasaur | * managed to get it to build the swift package fine (add swift and swiftpm to buildInputs, set dontUseSwiftpmBuild, possibly patch build.rs in that subdirectory), but it had linking errors | 18:23:50 |
| samasaur | am actively on the way to the airport rn but will post the work I did when I get a chance | 18:24:13 |
| Randy Eckenrode | I have a fix. This issue was due to a GCC 15 fix that only works on glibc. There was another patch proposed that fixes the failure in a portable way. I’m currently building to confirm. | 18:42:09 |
| Randy Eckenrode | https://github.com/NixOS/nixpkgs/pull/452676 | 18:44:09 |
| samasaur | running a nixpkgs-review on that now but it looks good to me | 19:06:26 |
| samasaur | ugh it needs a linux builder for some reason? | 19:08:28 |
| samasaur | nvm then | 19:08:31 |
| Randy Eckenrode | Should I retarget staging? | 19:09:42 |
| Randy Eckenrode | The rebuild count isn’t high, but it rebuilds nixos-tests, which I guess is heavy? | 19:09:57 |
| samasaur | that seems reasonable | 19:15:53 |
| Randy Eckenrode | That’s what the tooltip for the label said, so I switched it to staging. | 19:16:09 |
| samasaur | here's my work on sentry-cli. it still fails with the following warnings:
sentry-cli> = note: ld: warning: directory not found for option '-L/nix/store/2rynnwc94yn21j5d4acci5ww4qgp4608-apple-sdk-14.4/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftObservation'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftCompatibilityConcurrency'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftObjectiveC'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftFoundation'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swift_StringProcessing'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftCoreFoundation'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swift_Concurrency'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftXPC'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftCompatibilityPacks'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftUniformTypeIdentifiers'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftIOKit'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftCoreGraphics'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftDarwin'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftCore'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftDispatch'
sentry-cli> ld: warning: Could not find or use auto-linked library 'swiftCompatibility56'
followed by a LOT of "unavailable symbol" errors
| 19:16:56 |
| samasaur | i won't be able to look at this for a bit but hopefully that is helpful. best of luck to anyone who tries, hopefully it's just adjusting the linking path | 19:26:05 |
| Randy Eckenrode | This patch works for me: https://gist.github.com/reckenrode/8bae7645d17a60f8659439e7944199cd. You need to use replaceVars with swiftLib = lib.getLib swift; on the patch. | 20:01:06 |
| Randy Eckenrode | $ result/bin/sentry-cli --version
sentry-cli 2.56.1
| 20:01:20 |
 emily | I've been wondering if we should have a useful xcode-select in stdenv… | 21:24:21 |
| Randy Eckenrode | Maybe for 26.05. People might get cranky about it in impure dev shells though. | 23:41:55 |
| 17 Oct 2025 |
| samasaur | https://github.com/NixOS/nixpkgs/pull/452812 | 04:31:39 |
|  @cve:entropia.de changed their display name from cve (she/they) to cve. | 05:30:27 |
|  kumavis joined the room. | 07:26:10 |
 Ihar Hrachyshka | what's the latest with app linking / copying? I bumped nix-darwin and hm; I see a symlink under ~/Applications/Home Manager Apps. Spotlight doesn't show the apps. do we still have to copy apps with a custom module, like in Randy's nix config as before? | 15:08:18 |
