| 3 Nov 2025 |
Katie | I wanted to ask if there was rationale on the pipe operator being gated behind a different feature flag in Lix than in Nix | 20:46:59 |
Katie | I couldn't find one? But Google sucks now, so I don't necessarily feel confident that means one isn't written down somewhere. | 20:48:06 |
Katie | (For reference in Nix the flag is pipe-operators (plural) whereas it seems Lix uses pipe-operator (singular) | 20:48:55 |
Katie | * For reference in Nix the flag is pipe-operators (plural) whereas it seems Lix uses pipe-operator (singular) | 20:49:37 |
@dawnofmidnight:catgirl.cloud | Lix currently only implements the forward pipe (|>), not both | 20:49:52 |
Katie | Ohhh interesting | 20:50:05 |
Katie | That makes sense | 20:50:24 |
@dawnofmidnight:catgirl.cloud | nevermind, i just tried it and may be incorrect? (lix 2.94.0pre-acf6e1c) | 20:52:55 |
@dawnofmidnight:catgirl.cloud | * nevermind, i just tried it and may be incorrect? (lix 2.94.0pre-acf6e1c) both seem to work | 20:54:05 |
@dawnofmidnight:catgirl.cloud | ah, it was that it's not guaranteed it'll be kept around https://matrix.to/#/!9IQChSjwSHXPPWTa:lix.systems/$m2XyHW25YQPEPcOVgpyZ8cN-WLFgwJUPm3HsXI7iAUY?via=lix.systems&via=matrix.org | 20:58:12 |
@dawnofmidnight:catgirl.cloud | * ah, it was that it's not guaranteed the backwards pipe will be kept around, see https://matrix.to/#/!9IQChSjwSHXPPWTa:lix.systems/$m2XyHW25YQPEPcOVgpyZ8cN-WLFgwJUPm3HsXI7iAUY?via=lix.systems&via=matrix.org | 20:58:29 |
Katie | And it looks like the Lix impl predates the Nix one | 21:04:26 |
Katie | I imagine Lix also may have simply named the flag after the RFC (which would be sensible) so Nix NOT doing that is... annoying | 21:05:16 |
Katie | Okay, thank you very much! | 21:06:41 |
Katie | Another question: How does nix-darwin detection work? I keep running the uninstaller but /nix/nix-installer uninstall keeps claiming to detect it | 21:24:04 |
Katie | * Another question: How does nix-darwin detection work? I keep running the uninstaller but /nix/nix-installer uninstall keeps claiming to detect it EDIT: Okay, I think I figured this one out on my own, I don't think I read far enough here: https://git.lix.systems/lix-project/lix-installer#uninstalling | 21:28:13 |
Katie | * Another question: How does nix-darwin detection work? I keep running the uninstaller but /nix/nix-installer uninstall keeps claiming to detect it EDIT: Okay, I think I figured this one out on my own, I don't think I had read far enough here: https://git.lix.systems/lix-project/lix-installer#uninstalling | 21:34:00 |
| 4 Nov 2025 |
| whispers (it/fae) joined the room. | 00:45:18 |
| @dawnofmidnight:catgirl.cloud left the room. | 00:48:32 |
| yamabukiiro joined the room. | 03:38:36 |
| cafkafk changed their profile picture. | 08:23:30 |
| ncfavier changed their profile picture. | 23:55:14 |
| 5 Nov 2025 |
| UlyssesZhan joined the room. | 04:57:29 |
aleksi | Has anybody else encountered a segfault in the Clang linker, when cross-compiling Lix x86_64-linux->armv7l-linux? | 11:33:52 |
aleksi | [110/386] armv7l-unknown-linux-gnueabihf-clang++ -o lix/libutil/liblixutil.so lix/libutil/liblixutil.so.p/archive.cc.o lix/libutil/liblixutil.so.p/args.cc.o lix/libutil/liblixutil.so.p/async-io.cc.o lix/libuti>
FAILED: lix/libutil/liblixutil.so
armv7l-unknown-linux-gnueabihf-clang++ -o lix/libutil/liblixutil.so lix/libutil/liblixutil.so.p/archive.cc.o lix/libutil/liblixutil.so.p/args.cc.o lix/libutil/liblixutil.so.p/async-io.cc.o lix/libutil/liblixut>
clang++: warning: argument unused during compilation: '-Wa,--compress-debug-sections' [-Wunused-command-line-argument]
/nix/store/p62fsx79cp4ml2mrpxhlk52xxa7x6ns4-armv7l-unknown-linux-gnueabihf-binutils-wrapper-2.44/bin/armv7l-unknown-linux-gnueabihf-ld: line 273: 1390 Segmentation fault (core dumped) /nix/store/yp8bf0w3w>
clang++: error: linker command failed with exit code 139 (use -v to see invocation)
| 11:34:08 |
aleksi | * armv7l-unknown-linux-gnueabihf-clang++ -o lix/libutil/liblixutil.so lix/libutil/liblixutil.so.p/archive.cc.o lix/libutil/liblixutil.so.p/args.cc.o lix/libutil/liblixutil.so.p/async-io.cc.o lix/libutil/liblixutil.so.p/canon-path.cc.o lix/libutil/liblixutil.so.p/cgroup.cc.o lix/libutil/liblixutil.so.p/compression.cc.o lix/libutil/liblixutil.so.p/compute-levels.cc.o lix/libutil/liblixutil.so.p/config.cc.o lix/libutil/liblixutil.so.p/current-process.cc.o lix/libutil/liblixutil.so.p/deprecated-features.cc.o lix/libutil/liblixutil.so.p/english.cc.o lix/libutil/liblixutil.so.p/environment-variables.cc.o lix/libutil/liblixutil.so.p/error.cc.o lix/libutil/liblixutil.so.p/escape-char.cc.o lix/libutil/liblixutil.so.p/escape-string.cc.o lix/libutil/liblixutil.so.p/experimental-features.cc.o lix/libutil/liblixutil.so.p/file-descriptor.cc.o lix/libutil/liblixutil.so.p/file-system.cc.o lix/libutil/liblixutil.so.p/fmt.cc.o lix/libutil/liblixutil.so.p/git.cc.o lix/libutil/liblixutil.so.p/hash.cc.o lix/libutil/liblixutil.so.p/hilite.cc.o lix/libutil/liblixutil.so.p/json-utils.cc.o lix/libutil/liblixutil.so.p/logging.cc.o lix/libutil/liblixutil.so.p/monitor-fd.cc.o lix/libutil/liblixutil.so.p/mount.cc.o lix/libutil/liblixutil.so.p/namespaces.cc.o lix/libutil/liblixutil.so.p/position.cc.o lix/libutil/liblixutil.so.p/print-elided.cc.o lix/libutil/liblixutil.so.p/processes.cc.o lix/libutil/liblixutil.so.p/references.cc.o lix/libutil/liblixutil.so.p/regex.cc.o lix/libutil/liblixutil.so.p/serialise.cc.o lix/libutil/liblixutil.so.p/shlex.cc.o lix/libutil/liblixutil.so.p/signals.cc.o lix/libutil/liblixutil.so.p/source-path.cc.o lix/libutil/liblixutil.so.p/strings.cc.o lix/libutil/liblixutil.so.p/suggestions.cc.o lix/libutil/liblixutil.so.p/tarfile.cc.o lix/libutil/liblixutil.so.p/terminal.cc.o lix/libutil/liblixutil.so.p/thread-name.cc.o lix/libutil/liblixutil.so.p/thread-pool.cc.o lix/libutil/liblixutil.so.p/unix-domain-socket.cc.o lix/libutil/liblixutil.so.p/url-name.cc.o lix/libutil/liblixutil.so.p/url.cc.o lix/libutil/liblixutil.so.p/users.cc.o lix/libutil/liblixutil.so.p/xml-writer.cc.o -flto -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,-soname,liblixutil.so -fsanitize=signed-integer-overflow -fsanitize-undefined-trap-on-error -shared-libsan -pthread -Wl,--no-copy-dt-needed-entries -Wl,--start-group /nix/store/g467h9kds325j3qbx89y8f460di2aa75-aws-sdk-cpp-armv7l-unknown-linux-gnueabihf-1.11.448/lib/libaws-cpp-sdk-core.so /nix/store/g467h9kds325j3qbx89y8f460di2aa75-aws-sdk-cpp-armv7l-unknown-linux-gnueabihf-1.11.448/lib/libaws-cpp-sdk-s3.so /nix/store/jzfhg64w6ma28gnzskaprafjjd9y4cb4-boehm-gc-armv7l-unknown-linux-gnueabihf-8.2.8/lib/libgc.so -lpthread -ldl /nix/store/kgdd79qn2hk82azala1g4ppwf8qrdgnd-boost-armv7l-unknown-linux-gnueabihf-1.87.0/lib/libboost_container.so.1.87.0 /nix/store/s7fa63wvd1y5278lh1rhy2d2ncy32mpi-libseccomp-armv7l-unknown-linux-gnueabihf-2.6.0-lib/lib/libseccomp.so /nix/store/ipzk6pqaqh7d4gyybflpbkw3gxbj4kxz-libarchive-armv7l-unknown-linux-gnueabihf-3.8.0-lib/lib/libarchive.so /nix/store/vg27sszdgp4jfrzmd973sxk5cywq0cdc-brotli-armv7l-unknown-linux-gnueabihf-1.1.0-lib/lib/libbrotlicommon.so /nix/store/vg27sszdgp4jfrzmd973sxk5cywq0cdc-brotli-armv7l-unknown-linux-gnueabihf-1.1.0-lib/lib/libbrotlidec.so /nix/store/vg27sszdgp4jfrzmd973sxk5cywq0cdc-brotli-armv7l-unknown-linux-gnueabihf-1.1.0-lib/lib/libbrotlienc.so /nix/store/cdmrkcwl24rrj1v8g5rixdw702fy27qm-openssl-armv7l-unknown-linux-gnueabihf-3.4.2/lib/libcrypto.so /nix/store/z0h9244p1cgrj1h9wj7fkc9qp0070ni4-capnproto-armv7l-unknown-linux-gnueabihf-1.1.0/lib/libkj-async.so /nix/store/z0h9244p1cgrj1h9wj7fkc9qp0070ni4-capnproto-armv7l-unknown-linux-gnueabihf-1.1.0/lib/libkj.so -Wl,--end-group
clang++: warning: argument unused during compilation: '-Wa,--compress-debug-sections' [-Wunused-command-line-argument]
/nix/store/p62fsx79cp4ml2mrpxhlk52xxa7x6ns4-armv7l-unknown-linux-gnueabihf-binutils-wrapper-2.44/bin/armv7l-unknown-linux-gnueabihf-ld: line 273: 1390 Segmentation fault (core dumped) /nix/store/yp8bf0w3wxh62w5xp5f161pkrfkm16am-armv7l-unknown-linux-gnueabihf-binutils-2.44/bin/armv7l-unknown-linux-gnueabihf-ld ${extraBefore+"${extraBefore[@]}"} ${params+"${params[@]}"} ${extraAfter+"${extraAfter[@]}"}
clang++: error: linker command failed with exit code 139 (use -v to see invocation)
| 11:35:38 |
K900 | This is not clang linker, it's GNU binutils linker | 13:24:38 |
aleksi | True, my mistake | 14:32:58 |
Cyborus | very minor question: is Lix pronounced like "Licks" or like "Leaks"? | 15:50:36 |
522 it/its ⛯ΘΔ | licks
it's on the faq, https://lix.systems/faq/ bottom question | 15:51:09 |