Using Haskell library packages - linker error
Hello, I am trying to set up Agda, and I have reduced it to a simpler problem: $ cat test.hs import Numeric.IEEE main = return () $ genv --pure --ad-hoc ghc@8.6 ghc-ieee754 gcc-toolchain % ghc test.hs Linking test ... ld: cannot find -lHSieee754-0.8.0-IfCS1Dp7pQVIOQRslM6kD collect2: error: ld returned 1 exit status `gcc' failed in phase `Linker'. (Exit code: 1) How can I fix this error? Am I doing something wrong, or is this a packaging bug? Regards, Jakub Kądziołka signature.asc Description: PGP signature
Re: Guix on Novena
On 2020-09-06, Andreas Enge wrote:
> On Wed, Sep 02, 2020 at 11:33:22AM -0700, Vagrant Cascadian wrote:
>> Yes, I would recommend installing Guix System directly to SATA, since
>> u-boot can boot from SATA partitions marked bootable (either MBR or GPT
>> though what GPT calls it I forget), and SATA will perform better, of
>> course.
>
> So far, I am using an external USB disk, which probably is not in the
> boot sequence.
From the u-boot prompt:
printenv boot_targets
Should output something like:
mmc1 mmc0 sata0 usb0 pxe
Doing:
setenv boot_targets usb0
Might get it to boot from usb only... I've also had occasional troubles
with some USB ports on the novena, so you might need to move it between
ports to find one that works consistantly.
> This is why the configuration has this:
> (bootloader (bootloader-configuration
>(bootloader u-boot-novena-bootloader)
>(target "/dev/mmcblk1")))
> to boot from the SD card. By the way, why /dev/mmcblk1, which also appears
> in the installation-os? Is this valid when an additional SATA disk is plugged
> in? My SD card is called /dev/mmcblk0, and there are several partitions;
> do I give /dev/mmcblk0 or /dev/mmcblk0p1 as the argument?
The bootloader needs to be installed on the raw SD device, not a
partition, so /dev/mmcblk0 or /dev/mmcblk1 (or if you're installing the
bootloader using an sd-to-usb adapter, /dev/sd{a,b...}).
I'm not sure if the bootloader can be installed on the full-sized SD
slot, but certainly works with the annoying microSD slot. Sometimes the
enumeration of the device number may vary from one kernel version or
even boot to the next (though it's gotten more stable in recent years).
I forget off the top of my head how you can pass a no-op to the boot
configuration to just generate the extlinux.conf that is used by u-boot,
but that's also an option to relying on the existing boot loader,
presuming it supports all the features you need to boot (e.g. u-boot's
distro_boot support).
> Then later I have:
> (file-systems (cons* (file-system
> (device (uuid
> "f1062993-3776-47d2-8900-9e4f1d9fc8aa")) ; /dev/sda1
> (mount-point "/")
> (type "ext4"))
>%base-file-systems))
> so that the store and everything else should be on the disk.
>
> Will this separation work?
Should be fine, yes.
> Will mounting /dev/sda1 to /mnt and issuing "guix system init config.scm /mnt"
> work? (The handbook suggests to do "herd start cow-store /mnt", but I forgot
> what this is needed for.) Will it populate only /mnt/gnu/store, or also
> /gnu/store from the place where I call "guix system init"? Since the latter
> is almost full.
Someone else will have to answer this; it's been too long since I've
installed that way.
Thanks for working on getting some armhf build machines going!
After nearly a full day of building guile-static, I finally managed to
get the novena installation updated to a recent guix, running
linux-libre@5.8 (as well as testing 5.4 and various
linux-libre-arm-generic builds).
live well,
vagrant
signature.asc
Description: PGP signature
Re: Guix on Novena
Hello, sorry for what are probably silly questions, I have difficulties wrapping my head around how installation works. I am attaching my current configuration, copy-pasted from our Overdrive machines and augmented by snippets from yours, Vagrant. Right now I am on Debian with Guix as package manager, running from the SD card. After reading up through the last half year of guix-devel and help-guix, I realise that I could have followed https://lists.gnu.org/archive/html/help-guix/2020-04/msg00051.html ; apparently guix system disk-image -e "(@ (gnu system install) novena-installation-os)" executed on an aarch64 machine should have created a bootable SD card image with only Guix. Something to try next time! (By the way, swapping the micro-SD card is rather finicky on this board, and I try to avoid it). On Wed, Sep 02, 2020 at 11:33:22AM -0700, Vagrant Cascadian wrote: > Yes, I would recommend installing Guix System directly to SATA, since > u-boot can boot from SATA partitions marked bootable (either MBR or GPT > though what GPT calls it I forget), and SATA will perform better, of > course. So far, I am using an external USB disk, which probably is not in the boot sequence. This is why the configuration has this: (bootloader (bootloader-configuration (bootloader u-boot-novena-bootloader) (target "/dev/mmcblk1"))) to boot from the SD card. By the way, why /dev/mmcblk1, which also appears in the installation-os? Is this valid when an additional SATA disk is plugged in? My SD card is called /dev/mmcblk0, and there are several partitions; do I give /dev/mmcblk0 or /dev/mmcblk0p1 as the argument? Then later I have: (file-systems (cons* (file-system (device (uuid "f1062993-3776-47d2-8900-9e4f1d9fc8aa")) ; /dev/sda1 (mount-point "/") (type "ext4")) %base-file-systems)) so that the store and everything else should be on the disk. Will this separation work? Will mounting /dev/sda1 to /mnt and issuing "guix system init config.scm /mnt" work? (The handbook suggests to do "herd start cow-store /mnt", but I forgot what this is needed for.) Will it populate only /mnt/gnu/store, or also /gnu/store from the place where I call "guix system init"? Since the latter is almost full. Thanks for your enlightenment, Andreas ;; GuixSD configuration file for the Novena build machines. ;; Copyright © 2016, 2017, 2018 Ludovic Courtès ;; Copyright © 2019, 2020 Andreas Enge (guix-configuration (inherit config) (use-substitutes? #f) (max-silent-time 7200) (authorized-keys %authorized-guix-keys)) (packages (cons* screen openssh u-boot-novena vim %base-packages)))
Re: Problems with McCLIM (Common Lisp)
Konrad Hinsen writes: > That sounds good, as does getting rid of ADSF bundles. I have more or > less given up on numcl, for example, which fails to compile to a bundle > in recent versions but seems to work find via fasls (at least it works > fine with quicklisp). It seems that the Common Lisp community is mostly relying on Quicklisp and thus rarely, if ever, uses asdf:compile-bundle-op. The latter has been a source of oddities to me: several times a piece of code would behave differently between compile-bundle-op and compile-op. Upstream is almost always relying on compile-op and thus not aware of the compile-bundle-op issues. Cheers! -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature
