<bavier1>holamundo: the manual, and maybe just perusing the existing packages
<bavier1>OriansJ: definitely send an update to guix-devel, I'd be interested to hear more about your project
<bavier1>I'm off-and-on playing with the bootstrap-compiler idea too
<OriansJ>bavier1: it is literally a full bootstrap from a single 280 byte binary [Hex monitor] to include a text editor, assembler, linker and now a forth. Each piece written in the pieces created before them and the core binary is available in hex and assembly [Only 160 instructions]
<OriansJ>With prototypes written in C for some of the harder to grep pieces, lots of comments and a VM which can run in under 64KB
<OriansJ>Its been largely a fun hobby for me. But to be honest a few of the parts needed to do a proper hex bootstrap were a MASSIVE pain in the ass.
<OriansJ>creating the text editor, using only a hex monitor was a serious lesson in patience. Creating the web IDE in python and having it load a library built from the source of the VM was actually alot of fun
<OriansJ>all of the pieces have fully deterministic builds and produce identical checksums, even when run on some quite exotic hardware.
<Apteryx>Yeah, I got that too! It seems the file is empty by default. I had to use the installed wicd-client to set some static DNS addresses which I got from my IP. Not sure if this is a bug or if I should be configuring something more in my config.scm.
<kadintrooper>Ugh I really don't want to go through the entire install guide again
<Apteryx>There probably is one installed for you, and you don't need to be aware of it.
<Apteryx>From archlinux's "boot loaders" page: "In order to boot Arch Linux, a Linux-capable boot loader must be installed to the Master Boot Record or the GUID Partition Table. It is the first piece of software started by the BIOS or UEFI. It is responsible for loading the kernel with the wanted kernel parameters, and initial RAM disk before initiating the boot process."
<kadintrooper>My drive is encrypted, turn the computer on, put in my password and kicks me to tty
<ng0>Apteryx: that's not what I meant, nice or not. What I do is thinking about and working on a system which uses GuixSD as a base. When it can be integrated almost 1:1 with Guix, I'm more than happy, the only problem I see is coverage of hardware of linux-libre. There are a number of solutions I have for this, but if the difference in wifi and graphics isn't so big anymore I'd try to roll with linux-libre and
<ng0>think about solutions for more open support later on my roadmap
<ng0>getting blobs back into linux-libre would mean shipping our own linux definition, which will be terrible if people decide to init the system on bare metal and then do a guix pull
<adfeno>Any of you using GNUnet and with errors that ARM isn't running when issueing `gnunet-arm -I`?
<csanchezdll>building guile fails on tests due to the libgcc_s need for pthreads and the substitution hack on gcc being tailored for i386 only
<csanchezdll>main problem is building time, my ibook g4 is really slooooow
<csanchezdll>and now I will need to rebuild gcc-final which will retrigger a lot of builds
<csanchezdll>but I am learning a lot... for example the dynamic linker change in gcc also needed some tweaking for powerpc
<civodul>csanchezdll: yeah gcc.scm modifies gnu-user*.h for that, but perhaps you need to extend that pattern to match the ppc files
<csanchezdll>I had never really known how the dynamic binaries worked internally
<csanchezdll>civodul: yes I have seen it, the substitutions need a bit of reworking to apply to powerpc
<csanchezdll>thats the reason I wanted to see how source code looked like after pre-configure phase
<ng0>okay... next time I take notes. So there was something about curl which currently is bad and can be extended with no breakage om other distros, it was something about inconsistent environment variables, but what was the environment variable? anyone remember this? curl_ca_path?
<ng0>like it is used in most places, but some occurences of absolute/relative pathnames still exist?
<ng0>I want to fix this for gnurl-7.51.0, I fail to find the email this was mentioned in
<quigonjinn`>ng0: this must be the problem with kicad's github plugin as well, which uses curl
<ng0>I think there were occurences of a presumed default "/etc/...." ?
<ng0>just guessing so I can narrow down what to search for
<ng0>and to make sure I'm not imagining a discussion which never happened
<ng0>greping for things, now it feels like there was no discussion last month.. strange
<ng0>quigonjinn`: could it be that we use CURL_CA_PATH wrong?
<ng0>I'll spend the evening reading relevant sources before pushing the update
<quigonjinn`>ng0: i actually didn't know the existence of the CURL_CA_PATH envronment variable. I'll have to check that
<rekado>I don’t have time to search the sources for you right now
<ng0>what I mean is, do you have any threads on guix-devel (wasn't succesful in searching) where the problem is obvious? I've seen some default paths in the sources, but you seem to know more about the problem than I do.
<ng0>there was also no obvious bug report on curl, so someone should create one. there it could be made obvious what needs to be fixed in curl/gnurl. I can't report it, because I have no idea what exactly needs to be fixed.