<catonano>ng0: it's a way to say I heard in Berlin. When you start doing a task and you realize there are defects in the libraries, the compilers, so you start doing something absolutely unrelated to your original task: yak shaving
<OriansJ``>rain1: the really nice thing about janneke's recent commits is by enabling ELF sections to work with HEX2, he also enabled them for M0 as well. So we are going to have excellent support for x86/amd64
<OriansJ``>as you can see, it is trivial to add new instructions (a simple DEFINE)
<OriansJ``>so, assuming you don't screw up the encoding (definitely possible with x86 weirdness) of the Definitions, we have the simplest x86 assembler in existence that also supports all x86 instructions
<jamesrichardson>I installed libreoffice earlier today, I think it ended up compiling it. When the app opens all the letters look like boxes. Is this a font issue, locale issue, compile issue or user issue? Don't really know where to start troubleshooting.
<reepca>I'll try installing it and see what happens after I update
<OriansJ``>sneek: later tell janneke he can still use gdb to debug the MESCC_Tools hex.M0 prototype. Simply readelf -h test/results/test1-binary to get the entry address, b *0x600078 and layout asm should allow you with stepi/nexti to single step the assembly in a reasonable fashion. I can provide more if he wants.
<sneek>janneke, OriansJ`` says: that I have a present for him. (a hex assembler written in M0 for AMD64)
<sneek>janneke, OriansJ`` says: he can still use gdb to debug the MESCC_Tools hex.M0 prototype. Simply readelf -h test/results/test1-binary to get the entry address, b *0x600078 and layout asm should allow you with stepi/nexti to single step the assembly in a reasonable fashion. I can provide more if he wants.
<janneke>that's very good news, very cool OriansJ``
<reepca>Question, in the guile code, when we say "pairs", do we mean ("key" . "value") or ("key" "value")?
<efraim>I've been told the first is called 'a dotted pair' so it could be both options
<janneke>reepca: i think it rather means: (car . cdr) than "key" "value"
<jsierles>i'm trying to get guix working again after the recent issue with 'guix package' hanging forever. I followed instructions from the bug report, which suggested to download and build guix without substitutes. however the build consistently fails: building of `/gnu/store/k5zxs6rfyqsx292i1vzl1y3k3jwnlcj4-python-3.5.3.drv' timed out after 3600 seconds of
<sneek>ng0_, reepca says: It seems that the radeon hd 6450 does not work with linux-libre. Firmware fails to load, no 3D acceleration, one display output only, and a very messed up one at that. On the bright(?) side, I get to write a strongly-worded letter now.
<jsierles>i have some issues using the built-in julia package installer. it has various deps of course to compile. one of them is zlib. I've installed this but guessing julia needs a path set somewhere to find it.
<rekado>dadinn_: these directories exist when you boot into GuixSD
<dadinn_>rekado: my problem was that I was experimenting if I could bootsrap guix like debootstrap
<dadinn_>I wanted to chroot int a root environment without relying on a host system
<dadinn_>rekado: but there are no bash/sh binaries in the root profile
<dadinn_>obviously even if that worked it was a question whether there are necessary kernel/grub/cryptsetup/luks/zfs/etc packages available to install and set up the system to be bootable... but that's another question, I suppose the answer is no at the moment
<dadinn_>rekado: but that was my intent, reason i am looking for a shell to chroot into at least