From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Jon Loeliger <jdl@bigfootnetworks.com>,
"Philip A. Prindeville" <philipp_subx@redfish-solutions.com>,
linux-wireless@vger.kernel.org
Subject: Re: CRDA and cross-compilation
Date: Thu, 6 Aug 2009 11:42:46 -0700 [thread overview]
Message-ID: <43e72e890908061142w41d3c0e8x1dc81ffd3ac5b8ae@mail.gmail.com> (raw)
In-Reply-To: <1249580707.14919.29.camel@mj>
On Thu, Aug 6, 2009 at 10:45 AM, Pavel Roskin<proski@gnu.org> wrote:
> On Thu, 2009-08-06 at 09:56 -0700, Luis R. Rodriguez wrote:
>
>> ACK, is it possible to make it simpler?
>
> OK, here's my take.
>
> We only need a native compiler to verify regulatory.bin. I believe it's
> orthogonal to building CRDA.
>
> For someone doing a cross-compilation, it makes no sense to verify the
> installed regulatory.bin. Thus, the verification should be optional.
>
> But the compilation of regdbdump shouldn't be. Firstly, it's installed
> by "make install". Secondly, somebody may want to verify regulatory.bin
> on the target system.
>
> Here's the patch:
>
>
> crda: make it possible to disable verification
>
> Signed-off-by: Pavel Roskin <proski@gnu.org>
> ---
> Makefile | 7 +++++--
> 1 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index b93b735..3cc61c2 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -24,7 +24,9 @@ PUBKEY_DIR?=pubkeys
>
> CFLAGS += -Wall -g
>
> -all: $(REG_BIN) crda intersect verify
> +all: all_noverify verify
> +
> +all_noverify: crda intersect regdbdump
You removed REG_BIN from here, was that intentional?
> ifeq ($(USE_OPENSSL),1)
> CFLAGS += -DUSE_OPENSSL `pkg-config --cflags openssl`
> @@ -74,11 +76,12 @@ $(REG_BIN):
> $(NQ) ' EXIST ' $(REG_BIN)
> $(NQ)
> $(NQ) ERROR: The file: $(REG_BIN) is missing. You need this in place in order
> - $(NQ) to build CRDA. You can get it from:
> + $(NQ) to verify CRDA. You can get it from:
> $(NQ)
> $(NQ) $(REG_GIT)
> $(NQ)
> $(NQ) "Once cloned (no need to build) cp regulatory.bin to $(REG_BIN)"
> + $(NQ) "Use \"make noverify\" to disable verification"
> $(NQ)
> $(Q) exit 1
>
>
> --
> Regards,
> Pavel Roskin
>
next prev parent reply other threads:[~2009-08-06 18:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 8:08 CRDA and cross-compilation Philip A. Prindeville
2009-08-06 14:46 ` Jon Loeliger
2009-08-06 16:41 ` Pavel Roskin
2009-08-06 16:56 ` Luis R. Rodriguez
2009-08-06 17:38 ` Philip A. Prindeville
2009-08-06 17:45 ` Pavel Roskin
2009-08-06 18:30 ` Philip A. Prindeville
2009-08-06 18:41 ` Pavel Roskin
2009-08-06 18:42 ` Luis R. Rodriguez [this message]
2009-08-06 19:08 ` Pavel Roskin
2009-08-06 19:23 ` Luis R. Rodriguez
[not found] ` <4A7BD15E.1030604@redfish-solutions.com>
[not found] ` <43e72e890908070905s447a2fc0j2dc086048194db34@mail.gmail.com>
[not found] ` <4A7CC24D.1000104@redfish-solutions.com>
[not found] ` <1249698462.25983.7.camel@mj>
2009-08-10 22:13 ` [PATCH] " Philip A. Prindeville
2009-08-10 22:30 ` Luis R. Rodriguez
2009-08-10 23:55 ` Philip A. Prindeville
2009-08-11 0:25 ` Pavel Roskin
2009-08-11 0:41 ` Philip A. Prindeville
2009-08-11 5:52 ` Philip A. Prindeville
2009-08-11 0:41 ` Philip Craig
2009-08-11 0:45 ` Philip A. Prindeville
2009-08-06 19:14 ` Philip A. Prindeville
2009-08-06 19:21 ` Jon Loeliger
2009-08-06 15:09 ` John W. Linville
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=43e72e890908061142w41d3c0e8x1dc81ffd3ac5b8ae@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=jdl@bigfootnetworks.com \
--cc=linux-wireless@vger.kernel.org \
--cc=philipp_subx@redfish-solutions.com \
--cc=proski@gnu.org \
/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;
as well as URLs for NNTP newsgroup(s).