GNU bug report logs - #37286
Make a faster method to list supported boards.

Previous Next

Package: guix;

Reported by: Jesse Gibbons <jgibbons2357 <at> gmail.com>

Date: Mon, 2 Sep 2019 18:53:01 UTC

Severity: normal

Full log


View this message in rfc822 format

From: Jesse Gibbons <jgibbons2357 <at> gmail.com>
To: 37286 <at> debbugs.gnu.org
Subject: bug#37286: Make a faster method to list supported boards.
Date: Mon, 02 Sep 2019 12:52:49 -0600
There should be a faster way to list the supported boards with custom
versions of U-Boot.

From manual:
Many ARM boards require a specific variant of the U-Boot
(https://www.denx.de/wiki/U-Boot/) bootloader.

   If you build a disk image and the bootloader is not available
otherwise (on another boot drive etc), it’s advisable to build an image
that includes the bootloader, specifically:

     guix system disk-image --system=armhf-linux -e '((@ (gnu system
install) os-with-u-boot) (@ (gnu system install) installation-os) "A20-
OLinuXino-Lime2")'

   ‘A20-OLinuXino-Lime2’ is the name of the board.  If you specify an
invalid board, a list of possible boards will be printed.



I think an example of an invalid board is "dne-board", which (last I
checked) does not exist and probably never will exist. If I run the
following command:

guix system disk-image --system=armhf-linux -e '((@ (gnu system
install) os-with-u-boot) (@ (gnu system install) installation-os) "dne-
board")'

guix tries to build an entire system. It doesn't look like it checks if
"dne-board" is a valid board until it is building the image. It takes
hours to cross-compile the kernel, and even longer if the kernel needs
to be deblobbed. I have not yet been able to cross-compile any system
using this method.




This bug report was last modified 5 years and 285 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.