linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Jon Loeliger <jdl@bigfootnetworks.com>
Cc: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>,
	linux-wireless@vger.kernel.org
Subject: Re: CRDA and cross-compilation
Date: Thu, 06 Aug 2009 12:41:26 -0400	[thread overview]
Message-ID: <1249576886.14919.16.camel@mj> (raw)
In-Reply-To: <1249569993.6446.2.camel@jdl-desktop>

On Thu, 2009-08-06 at 09:46 -0500, Jon Loeliger wrote:
> On Thu, 2009-08-06 at 01:08 -0700, Philip A. Prindeville wrote:
> > Who currently owns CRDA?
> > 
> > I started to stare at cross-compiling issues, but realized that we need
> > two versions of reglib.o and print-regdom.o...
> > 
> > One to link with regdumpdb (compiled with HOSTCC) and one to link with
> > everything else (compiled with TARGET_CC)...
> > 
> > No easy way to do this without a lot of changes.
> 
> I posted a 5-part patch series to address this issue.
> To the best of my knowledge, it has not been applied yet.
> 
> You can find it here:
> 
> http://article.gmane.org/gmane.linux.kernel.wireless.general/35350

I objected against using the misleading use of the "TARGET" work in some
variables, but there was no reaction.  Failure to react to objections is
the likely reason it wasn't applied.

I also think that you add too much complexity to the Makefile.

Also, the use of .config is not common.  Most valuables can be specified
on the command line.  That would override the definitions in Makefile,
and that's how it's done.

For instance, you can have this in Makefile:

HOSTCC = gcc
CC = $(HOSTCC)

Running "make CC=/opt/mips/bin/gcc" would override CC but not HOSTCC.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2009-08-06 16:41 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 [this message]
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
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=1249576886.14919.16.camel@mj \
    --to=proski@gnu.org \
    --cc=jdl@bigfootnetworks.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=philipp_subx@redfish-solutions.com \
    /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).