Nixpkgs Stdenv | 220 Members | |
| 70 Servers |
| Sender | Message | Time |
|---|---|---|
| 15 Nov 2024 | ||
| ideally C++ wouldn't work like that | 10:42:12 | |
I wonder how viable it would be to just set -frandom-seed=0 and set it specifically in packages that would break | 10:42:28 | |
| https://github.com/NixOS/nixpkgs/issues/151475#issuecomment-1245992562 | 10:42:36 | |
I've been doing -frandom-seed=fixed in some projects and haven't become aware of ill effects but I do not know what the true generalised consequences might be. | 10:43:10 | |
| The need to have such a seed seems a bit bonkers from a reproducible builds standpoint | 10:43:33 | |
| The idea of hashing stuff in the compiler wrapper is really unappealing from a performance standpoint too | 10:44:06 | |
| it's because of C++ saying you can define things in multiple files and they shouldn't collide or whatever | 10:44:14 | |
| I want compiler wrappers to die anyway, so 😅 | 10:44:25 | |
btw, as a ca-derivations enjoyer you may enjoy this long but fruitful conversation I had with amjoseph on the Discourse about how we can achieve proper short-circuiting for shared libraries with stubs (like the macOS .tbds I was talking about) and splitting out linking into multiple steps https://discourse.nixos.org/t/why-does-the-nixos-infrastructure-have-to-be-hosted-in-a-centralized-way/46789/32 | 10:44:33 | |
| even header cleaning is relevant! | 10:44:39 | |
| (also this could dovetail with runtime performance improvements by doing the "dynamic loading" part of things at the time of the "relink" build) | 10:47:45 | |
| That's a great thread, thanks for sharing. | 11:08:30 | |
| I have a feeling I've read it before too. | 11:09:34 | |
| So, how to actually make some of these things happen? | 11:09:43 | |
| I guess there are two parts: 1) get fundamental infra inplace 2) an immense amount of grind to actually make it work sensibly in practice. | 11:10:34 | |
| I've come up with a possible use case for this abandoned PR https://github.com/NixOS/nixpkgs/pull/355000 Being able to put link-only flags in it for | 11:13:11 | |
| * I've come up with a possible use case for this abandoned PR https://github.com/NixOS/nixpkgs/pull/355000 Being able to put link-only flags in it for | 11:13:24 | |
| * I've come up with a possible use case for this abandoned PR https://github.com/NixOS/nixpkgs/pull/355000 Being able to put link-only flags in it for An alternative route would be to bracket these flags in | 11:14:38 | |
In reply to @emilazy:matrix.orgBtw the comment mentioned is not accurate | 11:14:41 | |
| Open Build System at least (optionally) rebuilds everything | 11:15:14 | |
| which comment? | 11:15:30 | |
| I don't see any mention of OBS there | 11:15:43 | |
In reply to @emilazy:matrix.orgThe comment you are linking to | 11:17:38 | |
| oh, "No other distro"? | 11:17:48 | |
| does openSUSE rebuild every downstream package for a one-byte security fix patch in OpenSSL that doesn't affect the headers or ABI? | 11:18:13 | |
| Just because other distros may pay the cost doesn't mean nixpkgs must also. | 11:18:36 | |
In reply to @p14:matrix.orgDon't get me wrong; I mean it's not something specific to Nixpkgs or Guix | 11:19:12 | |
| the world rebuilds are generally more gradual with other distros, AIUI | 11:20:18 | |
| involving manual pkgrel bumps etc. | 11:20:25 | |
In reply to @emilazy:matrix.orgI'm not sure if they added an automated function reference table or something similar when using the open build service. This process may be done manually, but based on my past experience with OBS, it should not be automatic | 11:20:49 | |