From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: Philip Craig <philipc@snapgear.com>
Cc: Pavel Roskin <proski@gnu.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Jon Loeliger <jdl@bigfootnetworks.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] CRDA and cross-compilation
Date: Mon, 10 Aug 2009 17:45:22 -0700 [thread overview]
Message-ID: <4A80BF22.9060101@redfish-solutions.com> (raw)
In-Reply-To: <4A80BE1F.8020708@snapgear.com>
Philip Craig wrote:
> Philip A. Prindeville wrote:
>> * allowing a cross-compilation without contamination by the host's own state via pkg-config bleeding into it.
>
> Setting PKG_CONFIG_LIBDIR should fix that without any makefile changes.
> I haven't tried with this package, but it works for every other
> cross compilation I've done.
Indeed, and that would work until, as Pavel points out, someone adds something naive and ill-informed like a `uname -r` (or `arch`) into the Makefile.
I'm not just trying to make the current version safe for cross-compilation, but all future versions too so I don't ever have to come back and fix this issue again.
You have no idea how many packages we had to make cross-compilation safe. Literally dozens. And some of them continue to have periodic regressions.
next prev parent reply other threads:[~2009-08-11 0:45 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
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 [this message]
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=4A80BF22.9060101@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=jdl@bigfootnetworks.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=philipc@snapgear.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.