From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] boot/barebox: license files hashes only valid for latest version
Date: Thu, 19 Mar 2020 19:04:46 +0100 [thread overview]
Message-ID: <20200319180446.GH10025@scaer> (raw)
In-Reply-To: <CAGm1_kvY1+5QbCX=vTB6AYRVESTVntm9AT+1tiSVifV8jH8Qyg@mail.gmail.com>
Yegor, All,
On 2020-03-19 14:32 +0100, Yegor Yefremov spake thusly:
> On Thu, Feb 6, 2020 at 8:44 PM Peter Korsgaard <peter@korsgaard.com> wrote:
> > We can only know the details of the license files for known versions. For
> > custom, older or newer versions, the license files may change, or may be
> > moved around.
> >
> > So, do for Barebox as was done for ATF, linux, and linux-headers, and
> > only define the list of license files for the latest version.
[--SNIP--]
> > diff --git a/boot/barebox/barebox.mk b/boot/barebox/barebox.mk
> > index 52178d89c8..f11f9950d1 100644
> > --- a/boot/barebox/barebox.mk
> > +++ b/boot/barebox/barebox.mk
> > @@ -33,7 +33,9 @@ endif
> >
> > $(1)_DEPENDENCIES = host-lzop
> > $(1)_LICENSE = GPL-2.0 with exceptions
> > +ifeq ($(BR2_TARGET_BAREBOX_LATEST_VERSION),y)
> > $(1)_LICENSE_FILES = COPYING
> > +endif
> >
> > $(1)_CUSTOM_EMBEDDED_ENV_PATH = $$(call qstrip,$$(BR2_TARGET_$(1)_CUSTOM_EMBEDDED_ENV_PATH))
>
> This approach works with barebox. But when I also use barebox-aux from
> git (for am335x), I get the following error:
>
> ERROR: No hash found for barebox-aux-1e23cf5c7b71c29cc8dd7b0c5b80929d286b554e.tar.gz
This error is not about the hash files, but about the actual downloaded
tarball, while the patch you are replying to is about the hash of the
license file.
Care to provide a defconfig, or even just the URL to that git repo,
please?
Regards,
Yann E. MORIN.
> package/pkg-generic.mk:167: recipe for target
> '/home/user/buildroot/bsp-experimental/build/barebox-aux-1e23cf5c7b71c29cc8dd7b0c5b80929d286b554e/.stamp_downloaded'
> failed
> make[1]: *** [/home/user/buildroot/bsp-experimental/build/barebox-aux-1e23cf5c7b71c29cc8dd7b0c5b80929d286b554e/.stamp_downloaded]
> Error 1
> Makefile:84: recipe for target '_all' failed
> make: *** [_all] Error 2
>
> Any idea how to fix this?
>
> Yegor
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-03-19 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 18:19 [Buildroot] [git commit] boot/barebox: license files hashes only valid for latest version Peter Korsgaard
2020-03-19 13:32 ` Yegor Yefremov
2020-03-19 18:04 ` Yann E. MORIN [this message]
2020-03-19 20:41 ` Yegor Yefremov
2020-03-19 21:59 ` Yann E. MORIN
2020-03-20 7:50 ` Yegor Yefremov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200319180446.GH10025@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox