unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Leo Famulari <leo@famulari.name>
Cc: 32982@debbugs.gnu.org
Subject: [bug#32982] [PATCH] gnu: u-boot: Update to 2018.09.
Date: Thu, 11 Oct 2018 13:57:21 -0700	[thread overview]
Message-ID: <875zy842xa.fsf@aikidev.net> (raw)
In-Reply-To: <20181011202335.GB7201@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

On 2018-10-11, Leo Famulari wrote:
> On Sun, Oct 07, 2018 at 08:16:47PM -0700, Vagrant Cascadian wrote:
>> * gnu/packages/bootloaders.scm (u-boot): Update to 2018.09.
>>   (u-boot-tools): Substitute "coverage" for "python-coverage".
>>   (u-boot-tools): Update workaround for only 99% test coverage.
>
> Thanks!
>
>>  (define u-boot
>>    (package
>>      (name "u-boot")
>> -    (version "2018.07")
>> +    (version "2018.09")
>
> For me, u-boot 2018.09 fails to build like this:
>
> ------
> $ ./pre-inst-env guix build -e '(@@ (gnu packages bootloaders) u-boot)'
> [...]
> starting phase `configure'
> source directory: "/tmp/guix-build-u-boot-2018.09.drv-0/u-boot-2018.09" (relative from build: ".")

I think u-boot itself is not a buildable package; there are numerous
packages that inherit from u-boot, such as u-boot-tools,
u-boot-wandboard, u-boot-novena, u-boot-cubieboard, etc.

Since each u-boot build is specific to a given target, I'm not sure what
a meaningful build of u-boot would be.


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2018-10-11 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08  3:16 [bug#32982] [PATCH] gnu: u-boot: Update to 2018.09 Vagrant Cascadian
2018-10-11 20:23 ` Leo Famulari
2018-10-11 20:57   ` Vagrant Cascadian [this message]
2018-10-11 21:29     ` bug#32982: " Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875zy842xa.fsf@aikidev.net \
    --to=vagrant@debian.org \
    --cc=32982@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).