| 13 Sep 2023 |
 Artturin | In reply to @winterqt:nixos.dev
Hi all, poking my head in to confirm some weird thing. Is it expected that libclang, if added to a derivation's nativeBuildInputs (strictDeps = false at that), will more or less completely blow up the ability to use Clang? (e.g. not being able to find any libc headers like stdbool.h.) Diff the dumped env vars | 22:31:35 |
| Artturin | * In reply to @winterqt:nixos.dev
Hi all, poking my head in to confirm some weird thing.
Is it expected that
libclang, if added to a derivation's nativeBuildInputs (strictDeps = false at that), will more or less completely blow up the ability to use Clang? (e.g. not being able to find any libc headers like stdbool.h.)
Diff the dumped env vars after the setup | 22:31:55 |
 Winter (she/her) | In reply to@artturin:matrix.org
Diff the dumped env vars That's what I'm doing, and nothing is different (after sorting + de-duping) that I've seen. | 22:31:56 |
| Winter (she/her) | It's definitely CMake-specific, but I'm still trying to figure out how, none of the CMAKE_* env vars are different in a substantial way (unless order matters, which it shouldn't). | 22:32:39 |
| Artturin | Is this just the normal package set and not a pkgsLLVM or so | 22:33:00 |
| Winter (she/her) | It's pkgsLLVM bc Darwin :/ | 22:34:58 |
| Winter (she/her) | FWIW I don't need it to be in nBI, I'm just trying to figure out why it breaks. | 22:35:23 |
| Winter (she/her) | (specifically because mkShell.packages won't work then) | 22:35:36 |
| Artturin | So build != host? | 22:35:41 |
| Artturin | In reply to @winterqt:nixos.dev
(specifically because mkShell.packages won't work then) .packages is bad anyways and the correct dependency attributes should be used | 22:36:50 |
| Winter (she/her) | In reply to @artturin:matrix.org
So build != host? build == host, this is a darwin build in a darwin machine + no strictDeps | 22:50:20 |
| Artturin | So it's not pkgsLLVM | 22:51:52 |
| Winter (she/her) | ah, that's what you were getting at | 22:52:49 |
| Winter (she/her) | correct, it's just import nixpkgs {} | 22:53:06 |
| Winter (she/her) | i'll diff the remaining cmake env vars, doubt it'll come up with anything though | 22:54:28 |
| Artturin | did you nix-diff the diffs | 23:26:40 |
| Artturin | * did you nix-diff the drv diffs | 23:26:50 |
| Artturin | and did you diff the envs after the cmake hook has run | 23:27:46 |
| Winter (she/her) | yes and yes | 23:28:50 |
| Winter (she/her) | the only thing that differs is the order of the paths in the env vars | 23:29:08 |
| Winter (she/her) | however, something odd i noticed: | 23:29:19 |
| Winter (she/her) | in the "everything in nBI" case, the cmake generated C_INCLUDES variable in the Makefile contains a bunch of include paths that the "everything where they should be" case doesn't have | 23:30:03 |
| Winter (she/her) | but there's nothing different in the env vars that would cause that, afaict | 23:30:16 |
| Winter (she/her) | found it, i think | 23:47:01 |
| Winter (she/her) | wow i hate computers | 23:47:16 |
| 14 Sep 2023 |
| Artturin | In reply to @winterqt:nixos.dev
found it, i think What was it? | 02:04:43 |
| Winter (she/her) | In reply to @artturin:matrix.org
What was it? somewhat broken special casing in the thing i'm trying to build, plus weird (at least to me) setup hook behavior
i'm trying to figure the setup hook part out, so two questions:
we have two packages, A, and B. A has propagatedBuildInputs = [ B ]. B has a setup hook.
- what offset is used when you put A in buildInputs? it seems that it would be discarded because the calculated offsets are
0, 2.
- is it expected that if A was put into nativeBuildInputs, B's setup hook isn't ran?
| 13:02:47 |
 trofi | Will cross-post here for general amusement as well:
Fun fact: nix has headers-only nlohmann_json dependency in it's output closure and pipewire has python. Chances are https://github.com/NixOS/nixpkgs/pull/255192 will fix it (more words: https://trofi.github.io/posts/298-unexpected-runtime-dependencies-in-nixpkgs.html).
| 22:14:07 |
| 15 Sep 2023 |
| Artturin | In reply to @trofi:matrix.org
Will cross-post here for general amusement as well:
Fun fact: nix has headers-only nlohmann_json dependency in it's output closure and pipewire has python. Chances are https://github.com/NixOS/nixpkgs/pull/255192 will fix it (more words: https://trofi.github.io/posts/298-unexpected-runtime-dependencies-in-nixpkgs.html).
Could it cause https://github.com/NixOS/nixpkgs/issues/41340 | 01:19:42 |
| Artturin | * In reply to @trofi:matrix.org
Will cross-post here for general amusement as well:
Fun fact: nix has headers-only nlohmann_json dependency in it's output closure and pipewire has python. Chances are https://github.com/NixOS/nixpkgs/pull/255192 will fix it (more words: https://trofi.github.io/posts/298-unexpected-runtime-dependencies-in-nixpkgs.html).
Could it cause https://github.com/NixOS/nixpkgs/issues/41340 on large closures | 01:20:41 |
