| 15 Mar 2026 |
 emily | it's non-PIE but it should be static PIE | 15:00:31 |
| emily | I think I tried to snipe @lt1379:matrix.org into it | 15:01:48 |
| emily | it's just switching a few flags in the stdenv adapters code or whatever (and then probably watching stuff break) | 15:02:54 |
| emily | well and also Go is annoying | 15:03:13 |
 Lun | you got me sniped as far as the watching stuff break part and not as far as having anything viable | 15:03:30 |
| emily | sunk cost fallacy let me down 😔 | 15:07:27 |
 dramforever | anyway this is a very funny problem | 16:33:14 |
| dramforever | where the qemu build thinks PIE works so it just enables it | 16:33:22 |
| dramforever | * where the qemu build thinks PIE works on aarch64-linux pkgsStatic so it just enables it | 16:33:36 |
| dramforever | which explodes | 16:33:40 |
| Lun | Think it came down to some issues with -shared and -static having -shared always win while -shared vs -static-pie is last entry wins and was going to need wrapper changes to even build stdenv, taking a look again in case I was overcomplicating it. | 17:24:20 |
| 4 Aug 2022 |
|  Winter (she/her) joined the room. | 03:27:09 |
|  [0x4A6F] joined the room. | 22:08:01 |
| 6 Aug 2022 |
| Winter (she/her) | Does anyone know where the fact that the Darwin stdenv builds CMake twice comes from? As far as I can tell, it's from stage 0, and then just gets used in the other stages from there. Am I missing something here, is it something with the overrides? It looks like it might be, but then the fact that those are only allowed in the final stage (per booter.nix) (when that doesn't seem true, since then they wouldn't be defined...?) comes up.
(Isn't this the same pattern (defining in one stage and referencing in the others) that makes Glibc only build a limited number of times in the Linux stdenv?) | 08:00:17 |
 @trofi:matrix.org | You think cmake should be rebuild less? Or more?
glibc's is probably a bit different as it's a part of stdenv.cc.libc and mainly used by that I would guess. Also, if depends if the package is used or not by other packages in the derivation would affect rebuild count as well.
| 14:59:09 |
| @trofi:matrix.org | Looking at stdenv's dep tree I see 2 cmake-boot hashes and one cmake hash: https://dpaste.com/8GGM6P9BF.txt | 15:03:11 |
| Winter (she/her) | In reply to @trofi:matrix.org
You think cmake should be rebuild less? Or more?
glibc's is probably a bit different as it's a part of stdenv.cc.libc and mainly used by that I would guess. Also, if depends if the package is used or not by other packages in the derivation would affect rebuild count as well.
I have no particular opinion, I'm just curious how that happens. | 21:22:09 |
| Winter (she/her) | Oh, for clarification, I was talking about cmake-boot. | 21:22:19 |
| Winter (she/her) | (which is cmake in the stdenv stages) | 21:22:29 |
| Winter (she/her) | see the line i linked | 21:22:36 |
| @trofi:matrix.org | AFAIU cmake = cmakeMinimal is only for stage1-4 (first build: bootstrapTools -> cmake-boot in pastebin). Last stage uses cmake as is. Also note that cmakeMinimal is used by zstd (used by final stage, does second build: stage4 -> cmake-boot -> zstd in pastebin). | 21:44:31 |
| @trofi:matrix.org | I used the following command to grep through the full depgraph: $ nix-store --query --graph $(nix-instantiate -A stdenv --argstr system x86_64-darwin) | 21:45:39 |
| 10 Aug 2022 |
|  luxus joined the room. | 09:55:36 |
| 17 Aug 2022 |
| @trofi:matrix.org | Quiz question: for a final glibc used in nixpkgs all over the place which gcc you think is used to build it on linux? a) Possible answers: gcc from bootstrap tools b) gcc from nixpkgs. | 17:36:21 |
| @trofi:matrix.org | You knew :) | 17:39:09 |
 Artturin | obviously it is the more ridiculous answer 🙃 | 17:40:03 |
| @trofi:matrix.org | Yeah :) Spoiler: https://dpaste.com/DMD34BUN9.txt | 17:40:23 |
| @trofi:matrix.org | * Quiz question: for a final glibc used in nixpkgs all over the place which gcc you think is used to build it on linux? Possible answers: a) gcc from bootstrap tools b) gcc from nixpkgs. | 17:42:06 |
 vcunat | AFAIK it isn't easy to do better. gcc links against glibc. So either somehow try replacing it later (rather hacky, probably) or build gcc twice during bootstrapping (will remain persistently annoying). Or as you suggest, update the bootstrapping tools more often. | 17:49:27 |
| vcunat | I might've missed some options. Or perhaps even confuse something. | 17:49:48 |
