| 21 Aug 2022 |
| greaka changed their display name from greaka ⚡️ to greaka . | 09:25:58 |
| 24 Aug 2022 |
hexa | John Ericson: can I have your opinion on this diff (staging-next -> staging)
diff --cc pkgs/development/compilers/llvm/git/libcxxabi/default.nix
index 441aba65166,2d4fe974c01..00000000000
--- a/pkgs/development/compilers/llvm/git/libcxxabi/default.nix
+++ b/pkgs/development/compilers/llvm/git/libcxxabi/default.nix
@@@ -61,7 -80,7 +80,11 @@@ stdenv.mkDerivation rec
postInstall = ''
mkdir -p "$dev/include"
++<<<<<<< HEAD
+ install -m 644 ../include/${if stdenv.isDarwin then "*" else "cxxabi.h"} "$dev/include"
++=======
+ install -m 644 ../../${pname}/include/${if stdenv.isDarwin then "*" else "cxxabi.h"} "$dev/include"
++>>>>>>> origin/staging-next
'';
meta = llvm_meta // {
| 22:16:01 |
hexa | moved into #staging:nixos.org 🙂 | 22:17:11 |
| underpantsgnome changed their display name from tinybronca to underpantsgnome. | 23:00:14 |
| 26 Aug 2022 |
| pennae joined the room. | 13:45:35 |
pennae | currently playing around with a mkDerivation' :: (Attrs -> Attrs) -> Attrs -> Drv. could be useful to solve eg the rust overrideAttrs problem (where rust would use mkDerivation' to do rust-specific processing to the args before passing them on, and regular mkDerivation would just pass id). is this something? is there something other than stdenv adapters that could turn into a problem? | 13:48:02 |
pennae | this hinges on overlayable mkDerivation, so the signature should really be mkDerivation' :: (Attrs -> Attrs) -> (Either Attrs (Attrs -> Attrs)) -> Drv i guess 🤔 | 13:50:42 |
Artturin | In reply to @pennae:matrix.eno.space currently playing around with a mkDerivation' :: (Attrs -> Attrs) -> Attrs -> Drv. could be useful to solve eg the rust overrideAttrs problem (where rust would use mkDerivation' to do rust-specific processing to the args before passing them on, and regular mkDerivation would just pass id). is this something? is there something other than stdenv adapters that could turn into a problem? I have rust overriding working in https://github.com/NixOS/nixpkgs/pull/179392 | 16:04:34 |
pennae | okay, let's use that :) | 16:23:22 |
| 30 Aug 2022 |
| aru joined the room. | 14:41:45 |
| aru left the room. | 15:54:41 |
| 7 Sep 2022 |
Winter (she/her) | what part of stdenv actually adds libraries to ldflags? i see where binaries are added to path and rpath is set, but not libraries... am i missing something obvious here? | 07:23:29 |
vcunat | bintoolsWrapper_addLDVars I think. | 07:30:19 |
Winter (she/her) | ahhh, i was thinking it would be in a different setup hook like that, no clue why grepping around wasn't helping there | 07:43:12 |
Winter (she/her) | thanks, i think you're right | 07:43:20 |
| 10 Sep 2022 |
| FRidh joined the room. | 06:11:17 |
| 14 Sep 2022 |
| pennae left the room. | 14:10:50 |
| 15 Sep 2022 |
| m_algery joined the room. | 12:48:24 |
| m_algery left the room. | 12:48:25 |
| 18 Sep 2022 |
| FRidh set a profile picture. | 17:20:58 |
| 23 Sep 2022 |
Winter (she/her) | npm ERR! Log files were not written due to an error writing to the directory: /homeless-shelter/.npm/_logs
npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
+ exitHandler
+ exitCode=226
+ set +e
+ '[' -n '' ']'
+ (( 226 != 0 ))
+ runHook failureHook
+ local hookName=failureHook
+ shift
+ local 'hooksSlice=failureHooks[@]'
+ local hook
+ for hook in "_callImplicitHook 0 $hookName" ${!hooksSlice+"${!hooksSlice}"}
+ _eval '_callImplicitHook 0 failureHook'
+ declare -F '_callImplicitHook 0 failureHook'
+ eval '_callImplicitHook 0 failureHook'
++ _callImplicitHook 0 failureHook
++ local def=0
++ local hookName=failureHook
++ declare -F failureHook
++ type -p failureHook
++ '[' -n '' ']'
++ return 0
+ return 0
+ '[' -n '' ']'
+ return 226
Compiling proc-macro2 v1.0.43
| 11:41:34 |
Winter (she/her) | does anyone know how it's possible for a command to "fail", run the failure hook, but then... keep going? | 11:41:53 |
Winter (she/her) | (i can't repro this on any machine other than the OfBorg builders so that's also fun) | 11:42:09 |
Winter (she/her) | (to be clear, the command that supposedly exited is... still going after the hook...) | 12:54:59 |
Winter (she/her) |
trap "exitHandler" EXIT
| 13:03:28 |
Winter (she/her) | which should not be possible! what even | 13:03:37 |
Winter (she/her) |
If a sigspec is 0 or EXIT, arg is executed when the shell exits.
| 15:14:55 |
Winter (she/her) | per bash manual | 15:14:58 |
Winter (she/her) | so... what? | 15:15:07 |
trofi | Might be a subshell? | 17:36:08 |