<brendyn>My /gnu/store is 18.8 GiB at the moment and I'm not even on GuixSD, just some stuff installed on parabola
<sturm>Hmm, I can't seem to "sudo guix pull" at the moment. Getting some warnings about "loading ....go failed ... bad header in object file", then continues and halts with "error: sed-hurd-path-max.patch: patch not found"
<sturm>(this is just normal "sudo guix pull" on GuixSD, not from a checkout)
<retard_>after "herd start cow-store /mnt I get "herd: exception caught while executing 'start' on service 'cow-store': invalid arguement", followed by "ERROR: In procedure mount: mount "/.rw-store" on "/gnu/store": Invalid arguement"
<retard_>Now I'm getting a different ERROR: in procedure rmdir: Device or resource busy.. what might this mean?
<alezost>sturm: it may be that your "guix" still uses Guile 2.0, but modules in ~/.config/guix/latest/ are compiled with Guile 2.2. Look at the first line of the guix script ("which guix"), and check what guile version it is
<catonano>git config user.name returns my real name and yet the patches prodced by git format-patch still use the nickname I used previously
<rain1>my compiler produces a kind of prescheme, lambdas are hoisted and nested expressions are denest to produce long LET*s
<OriansJ>rain1: We are going to have to work on your bootstrap but I think that'll be fun
<sturm>thanks alezost: based on your suggestions I switched root's "guix-latest" to point to the seemingly working version from my regular user account. The "sudo guix pull" then ran smoothly. My "system reconfigure" seems to be building webkitgtk though so I might have to come back tomorrow to see if it's all worked out :P
<janneke>ACTION just linked libc-mes.o + m.o -> m executable :-)
<OriansJ>rain1: so that the logic required to implement an assembler becomes trivial
<OriansJ>it literally becomes a trivial pattern matcher (DEFINE FOO FF00CCAA)
<OriansJ>where as for x86, you are going to have to create things like (DEFINE MOV_RSII 48c7c6) (DEFINE MOV_RAXI 48c7c0)
<OriansJ>aka x86 will require about 1,900 DEFINE lines to cover the encodings you probably want but stage0 only needs less than 250 lines
<rain1>hmm thats just too much, maybe instead of assembling x86 a langauge could be made from composite operations
<OriansJ>rain1: that is literally what a vm/bytecode interpreter does at run time and a O-code/bytecode compiler does at compile time
<ng0>I have just generated an initial x86_64 image of pragmaOS, with lots of parts still missing. Weights in at around 4GB already because of some of the graphical applications. My wish to use a different libc and compare sizes is justified. I hope this will not grow to 8GB when all applications are finished
<ng0>It looks so easy to maintain the build instructions and the whole process. disk-image is a cool function :)
<ng0>I want to compare musl and uclibc-ng builds. It has no high priority, I keep hacking on uclibc-ng on and off for months now.. the issue with it is that it's not just a package but is similar to a kernel build, but more compatible to glibc. But musl needs lots of patches, at least back o nGentoo
<janneke>what's the status on arm? running `guix environment guix' on latest master, i get
<janneke>builder for `/gnu/store/qf5ynngs5hkcjg4p9fn7v0i6ggg296vd-libgpg-error-1.24.drv' failed due to signal 4 (Illegal instruction)
<OriansJ>FOUND IT!!! Finally fixed the garbage collection bug in the High level prototype...
<quiliro>why is qwmu being installed on a default bare-bones.scm guix system init ?
<lfam>quiliro: To create swap with config.scm, you must first create a partition for swap in the normal way. Then, you can add (swap-devices '("/dev/foo")) to your config.scm. You'll need to change 'foo' to the right name.
<lfam>quiliro: I haven't done this before, but I think it should work
<lfam>Actually, I recently noticed that my GuixSD machine does need swap, because I saw the OOM messages in my /var/log/messages. But, I haven't noticed anything broken, so I'm ignoring it for now :)
<lfam>Yes, also for hibernation, but be careful if you set that up. There are caveats in a variety of cases. I think that GuixSD should handle this for the user so they have fewer opportunities to make mistakes.
<Sleep_Walker>it seems that documentation and code is out of sync - documentation use menu-entry, but it seems to be internal for gnu/bootloader/grub.scm and there is some new boot-parameters record which is undocumented
<lfam>Sleep_Walker: The web-based documentation or the documentation in the Git repo?
<lfam>The web-based documentation will almost always be out of sync, because it corresponds to the latest release. If the latest documentation in the Git repo is out of sync, that's a bug. Can you report it?
<rekado_>ng0: why bother with something other than the GNU libc at the bottom? Is this for a router?
<quiliro1>please remind me how i can make the new version of the usb beyond 0.12 that is published
<quiliro1>so i can boot in efi with guixsd installer
<ng0>rekado: yes, among other ideas. and also adding pieces into the puzzle framework of extending possibilities for Guix and GuixSD deployment
<rekado_>ng0: would you also set up a build farm to rebuild everything with that other libc? Or would users have to build everything from source?
<ng0>depends on our resources at that point and how we end up deploying pragmaOS builds, but the goal is to have an build-farm at some point to automate certain things. I don't expect users to build anything.
<quiliro>lfam: you told me that if /mnt/tmp was intact after power outage happened during installation, installation could be continued....should i follow the process in the guixsd installation manual as is (except for partitioning and partition formating)?
<ng0>alternative libc is at the very end of list of priorities.
<ng0>I'm also looking to either re-implement prep or write a parser for prep and add a reader for it to Haunt so that multi language pages generated from one document are possibel without the pain of pure xml
<ng0>as Haunt seems to have no opinion on anything it seems better than to continue writing my own simple generator
<ng0>which right now is using smu, make and optionally Guix