Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11186] New: Building wireless-regdb fails on BR 2018.05.1
Date: Wed, 25 Jul 2018 14:42:07 +0000	[thread overview]
Message-ID: <bug-11186-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=11186

            Bug ID: 11186
           Summary: Building wireless-regdb fails on BR 2018.05.1
           Product: buildroot
           Version: 2018.05
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: porto.rio at gmx.net
                CC: buildroot at uclibc.org
  Target Milestone: ---

When trying to build a BR-image with crda/wireless-regdb I get the following
error:

>>> wireless-regdb 2017.03.07 Extracting
xzcat /home/daemon/tfs/rpo2/dl/wireless-regdb/wireless-regdb-2017.03.07.tar.xz
| tar --strip-components=1 -C
/home/daemon/tfs/rpo2/work/porto/build/wireless-regdb-2017.03.07   -xf -
>>> wireless-regdb 2017.03.07 Patching
>>> wireless-regdb 2017.03.07 Configuring
>>> wireless-regdb 2017.03.07 Building
>>> wireless-regdb 2017.03.07 Installing to target
/usr/bin/install -m 644 -D -T
/home/daemon/tfs/rpo2/work/porto/build/wireless-regdb-2017.03.07/regulatory.bin
/home/daemon/tfs/rpo2/work/porto/target/usr/lib/crda/regulatory.bin
/usr/bin/install -m 644 -D -T
/home/daemon/tfs/rpo2/work/porto/build/wireless-regdb-2017.03.07/sforshee.key.pub.pem
/home/daemon/tfs/rpo2/work/porto/target/etc/wireless-regdb/pubkeys/sforshee.key.pub.pem
/usr/bin/install -m 644 -D -T
/home/daemon/tfs/rpo2/work/porto/build/wireless-regdb-2017.03.07/regulatory.db
/home/daemon/tfs/rpo2/work/porto/target/lib/firmware/regulatory.db
/usr/bin/install: cannot stat
'/home/daemon/tfs/rpo2/work/porto/build/wireless-regdb-2017.03.07/regulatory.db':
No such file or directory
package/pkg-generic.mk:304: recipe for target
'/home/daemon/tfs/rpo2/work/porto/build/wireless-regdb-2017.03.07/.stamp_target_installed'
failed
make[1]: ***
[/home/daemon/tfs/rpo2/work/porto/build/wireless-regdb-2017.03.07/.stamp_target_installed]
Error 1
Makefile:16: recipe for target '_all' failed
make: *** [_all] Error 2

The files "regulatory.db" and "regulatory.db.p7s" are missing in the used regdb
archive "wireless-regdb-2017.03.07.tar.xz"

Looking at the wireless-regdb.mk of BR 2018.05.1 I wonder why "05" is using
very old regdb 2017.03.07 when BR 2018.02.4 is using the much newer regdb
2018.05.31?

See
https://git.busybox.net/buildroot/tree/package/wireless-regdb/wireless-regdb.mk?h=2018.05.1
vs
https://git.busybox.net/buildroot/tree/package/wireless-regdb/wireless-regdb.mk?h=2018.02.4

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2018-07-25 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 14:42 bugzilla at busybox.net [this message]
2018-07-25 16:07 ` [Buildroot] [Bug 11186] Building wireless-regdb fails on BR 2018.05.1 bugzilla at busybox.net
2018-07-26  7:16 ` bugzilla at busybox.net

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=bug-11186-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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