!kyXJonZuBXCGzVwuSn:nixos.org

Systems Programming

286 Members
Kernel, stdenv, low-level hacking, patchelf, … 72 Servers

Load older messages


SenderMessageTime
21 Dec 2021
@linus.heckemann:matrix.mayflower.deLinux Hackerman joined the room.13:15:36
@linus.heckemann:matrix.mayflower.deLinux Hackerman
In reply to @mic92:nixos.dev
Take that! https://github.com/Mic92/tracedump/blob/main/tracedump/perf/cpuid.py
WHY
13:17:55
@dandellion:dodsorf.asDandellion joined the room.13:20:49
@k900:0upti.meK900 joined the room.13:23:49
@tnias:stratum0.orgtnias joined the room.13:25:33
@tomberek:matrix.orgtomberek joined the room.13:28:18
@moritz.hedtke:matrix.orgmoritz.hedtke joined the room.13:31:56
@mic92:nixos.devMic92
In reply to @linus.heckemann:matrix.mayflower.de
WHY
To avoid dependencies. Pip is not so great in general
13:35:38
@mic92:nixos.devMic92What the logo would be?13:38:26
@mic92:nixos.devMic92* What would the logo would be?13:38:44
@mic92:nixos.devMic92* What could the logo be?13:39:00
@wentasah:matrix.orgwentasah joined the room.14:05:52
@mic92:nixos.devMic92https://nixos.wiki/wiki/C#Use_a_clang_compiled_from_source I found a workaround this morning for using compilers build incrementally from git: https://nixos.wiki/wiki/C#Use_a_clang_compiled_from_source16:34:57
@mic92:nixos.devMic92* https://nixos.wiki/wiki/C#Use_a_clang_compiled_from_source I found a workaround this morning for using compilers build incrementally from source16:35:20
@fzakaria:matrix.orgfzakaria joined the room.16:42:57
@fzakaria:matrix.orgfzakariahi16:43:12
@fpletz:lodere.esfpletz joined the room.16:47:14
@gdamjan:spodeli.orggdamjan joined the room.17:51:57
@qubasa:gchq.icuQubasa joined the room.17:55:45
@qubasa:gchq.icuQubasa
In reply to @mic92:nixos.dev
https://nixos.wiki/wiki/C#Use_a_clang_compiled_from_source I found a workaround this morning for using compilers build incrementally from source
Ohh cool!
18:03:11
@fzakaria:matrix.orgfzakariafor those familiar with musl vs glibc trying to diagnose: https://github.com/seL4/musllibc/issues/1618:17:51
@charlotte:vanpetegem.mechvp joined the room.19:03:28
@mic92:nixos.devMic92 fzakaria: anything specific you want to know about musl? I would suggest to compile it from source and add a few printf statements in the code to track this down. 19:20:29
@mic92:nixos.devMic92the ld code is maybe a bit more complex than other parts of musl but not super hard. I read it quite a bit when building nix-ld.19:21:28
@andi:kack.itandi-speaking of lbc's has anyone looked at llvm's new libc?19:24:02
@andi:kack.itandi-Been thinking of switching to clang + clang-libc for my packagset as I am getting annoyed by GNU-things19:24:26
@mic92:nixos.devMic92I actually went to the university where L4 came from. All os devs are conditioned to microkernels there.19:24:31
@mic92:nixos.devMic92
In reply to @andi:kack.it
speaking of lbc's has anyone looked at llvm's new libc?
To me it seems like this project was more indented as research project to find out what to fix in clang to make it easier to build libc's. Are there any real-world users of this yet?
19:26:14
@andi:kack.itandi-I odn't know. I've only seen it about a month ago when the project page still stated "will be a project that does ....". So apparently very early in development.19:26:55
@andi:kack.itandi-https://llvm.org/docs/Proposals/LLVMLibC.html is that page19:27:26

Show newer messages


Back to Room ListRoom Version: 6