<OriansJ``>well janneke, how does this sound as an idea. How about we punt the problem like so: we fork Hex2 to make a specialized program that reads hex2 and only outputs binary symbol tables that are elf compatible and turn the elf generation into a binary stitching.
<janneke>OriansJ``: so, a separate program that (looks a bit/lot like the hex2 linker and) produces the elf footer: sym and str tables and we leave hex2 linker as is?
<mekeor>if i specify a the 'source'-field of a 'package' with 'local-file', there's no way to specify 'patches', is there?
<jonsger>rekado_: so guix pack -S /opt/gnu/bin=bin --target=armel-linux-gnu --system=armhf-linux diffutils should work?
<OriansJ``>reepca: all jumps (except JSR_COROUTINE) are relative and will only work to reach code that is within the 32KB jump range. Should you require a longer jump (say as large as the possible address space) JSR_COROUTINE exists for that purpose, simply load your target into the desired register and JSR_COROUTINE will always work.
<rekado_>mekeor: the “patches” field belongs to the “origin”. I think you may be able to use a “file://” URL instead of local-file. Would that work for you?
<cbaines>I'm installing GuixSD at the moment, and it's been building a lot of packages. I used the latest installation image, and did guix pull, but it's build linux, a load of Gnome related packages, and move as it's been running for several hours... is this to be expected?
<rekado_>cbaines: looks like a commit to master caused a rebuild of gtk and qt
<mekeor>cbaines: if you or rekado_ can determine which commit caused a rebuild of gtk and qt, you could use `guix pull --url=https://…COMMIT…` before you do `guix system init …`
<mekeor>(where COMMIT would be the hash of the commit before the commit which caused the rebuild)
<OriansJ``>sneek: later tell janneke that I probably will not take a crack at it until I finish figuring out the solution to reepca's disk operations request for FORTH (which means I also need to add the primitives to the VM spec)
<cbaines>mekeor, good idea, I'll try and see how many packages I've got remaining to build, and then consider that option
<cbaines>In general, I was pondering what it would be like to have some branch that followed master, but only advanced once there was a commit to advance to where some threshold was met about substitutes being available...
<OriansJ``>sneek: later tell janneke that with all of the modifications, I'll probably be changing the name of the M0 to M1 to reflect all of the enhancements over the M0 which is supposed to be the minimal Macro-assembler which can self-bootstrap
<sneek>janneke, OriansJ`` says: that I probably will not take a crack at it until I finish figuring out the solution to reepca's disk operations request for FORTH (which means I also need to add the primitives to the VM spec)
<sneek>janneke, OriansJ`` says: that with all of the modifications, I'll probably be changing the name of the M0 to M1 to reflect all of the enhancements over the M0 which is supposed to be the minimal Macro-assembler which can self-bootstrap
<rekado_>For some parts of Guix I’d like to have type annotations.
<reepca>That's one of the parts I really liked about common lisp
<rekado_>I would find this useful for monadic functions
<janneke>i should have a look at the typed racket thing
<janneke>goops can be quite useful, but i don't much like the magic of and restrictions on methods
<rekado_>it doesn’t have to be types — if we could express types with invariants or validators that would be just as useful
<koosha>rekado_: It's really crazy . I reinstalled GuixSD and in this time I gave the configuration file my device instead of label and also I wrote zero to the sector 33 so I didn't got that warning after installation and no error . But now I get that kernel panic again : |
<mekeor>is there any other reason to choose scheme to implement guix other than guile is a *GNU* high-level prog-lang?
<mekeor>does anybody use the emacs-package `use-package' within an emacs installed with guix? i have something like (use-package undo-tree). but although i have installed the guix-package "emacs-undo-tree", use-package installed "undo-tree" itself and created a directory ~/.emacs.d/elpa/undo-tree-….