Nixpkgs Stdenv | 230 Members | |
| 75 Servers |
| Sender | Message | Time |
|---|---|---|
| 23 Nov 2024 | ||
| it's just that we don't mangle them properly | 05:38:20 | |
| if the issue is invoking wrappers designed for AArch64 but feeding them 32-bit ARM code that's just a general problem of wrappers assuming one specific architecture | 05:38:53 | |
| using an unwrapped compiler probably makes more sense for that | 05:39:01 | |
| especially with LLVM | 05:39:17 | |
| Using an unwrapped compiler doesn't feel optimal, what if something needed to output 32-bit code on a 64-bit system but required libc or other stuff which the cc-wrapper needs. | 05:40:40 | |
| that won't work anyway because it'll be the 64-bit libc… | 05:40:57 | |
| so in that case you need another wrapper | 05:41:07 | |
| and rewrapping compilers is more of a pain than it ought to be right now, but that's a separate issue | 05:41:18 | |
| The other option is we just don't do any kernel hardening lol | 05:42:21 | |
| * The other option is we just don't do any kernel hardening via the stdenv lol | 05:42:36 | |
| I think the kernel has stuff for enabling hardening inside the config | 05:42:52 | |
| the simple option is just to use an unwrapped compiler for the VDSO build, since it should not be depending on libraries anyway given what the VDSO is | 05:43:00 | |
| How would we set the compiler just for the vdso? | 05:43:27 | |
| Would we have to build up to the vdso, change the CC for the vdso, and then finalize the build? | 05:44:01 | |
| Another option is to tune the hardening option, disable the zerocallregs hardening option when the derivation is set to build the vdso32 | 05:45:19 | |
| I'm not that familiar with the kernel build system, but I'd be surprised if there's no configuration knob for the compiler it uses to build 32-bit code like that | 05:46:42 | |
| After spending too long debugging runtime oddities I tracked the issue back to bad symlinks. Having read https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/setup-hooks/make-symlinks-relative.sh, I made a setup hook which checks for broken (or reflexive) symlinks: https://github.com/ConnorBaker/cuda-packages/blob/main/upstreamable-packages/noBrokenSymlinksHook/no-broken-symlinks-hook.sh Is there prior work for something similar? This is also based on the assumption that broken or reflexive symlinks are symptoms of a packaging problem. Are there cases where they are intended? | 08:57:48 | |
| There are definitely situations | 10:22:26 | |
| But not many | 10:22:27 | |
| I actually wanted that in stdenv for a while now | 10:22:37 | |
| I’d like to add the ability to detect cycles in references. Additionally, I’d love to simplify the logging statements so I don’t have to prefix the strings with the name of the setup hook. Any ideas if that’s a thing? | 19:53:57 | |
| 24 Nov 2024 | ||
| emily John Ericson Philip Taron (UTC-8) Randy Eckenrode & Artturin: have you guys seen this post (https://discourse.nixos.org/t/community-team-updates/56458) should we do a meeting to discuss things to add for a reply to the post or do we just want to message in here? | 02:36:45 | |
| p14: uh-oh.
| 03:28:29 | |
In reply to @rosscomputerguy:matrix.org(I'm going to work on a reply for the Darwin team. not sure what there is to say re: stdenv for the most part) | 03:34:52 | |
In reply to @rosscomputerguy:matrix.org* (I'm going to work on a reply for the Darwin team (w/ Randy). not sure what there is to say re: stdenv for the most part) | 03:35:20 | |
In reply to @emilazy:matrix.orgGotcha, yeah that's why I was asking before making a reply. We probably should discuss what to add for it. | 03:36:08 | |
In reply to @emilazy:matrix.orgThat error drives me crazy, especially when the extra arguments are out of your control. | 06:17:30 | |
| I think this might be a regression from the patch → wrapper change | 06:18:31 | |
In reply to @emilazy:matrix.orgHow are you hitting this? Is there any other context I have missed other than your message? | 11:44:37 | |
irods on staging | 11:44:55 | |