linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bender <pebender@san.rr.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: configure patch for cross compilation
Date: Wed, 02 Jun 2010 15:09:22 +0000	[thread overview]
Message-ID: <4C067422.5050607@san.rr.com> (raw)
In-Reply-To: <4C066A21.9090507@san.rr.com>

On 6/2/2010 7:57 AM, Kay Sievers wrote:
> On Wed, Jun 2, 2010 at 16:26, Paul Bender<pebender@san.rr.com>  wrote:
>> The message asking about cross compilation reminded me that I have a patch
>> that is needed for cross compilation. Because autoconf's AC_CHECK_FILE fails
>> when cross compiling, it use in location the pci.ids file needs to be
>> surrounded in a conditional. Otherwise, the configure script never allows
>> the --with-pci-ids-path to be used.
>
> Why would that fail? There are 3 test in a row, two of them are
> expected to always fail. If all of them will fail, if you must specify
> the thing on the commandline. That seems to work fine here.

I should not have used the term 'fail'. Rather, I should have used the 
term 'die'. The AC_CHECK_FILE macro checks to see whether or not the 
package is being cross compiled. If it is, then then it dies, causing 
the configure script to stop.

> And please never send compressed patches, especially not when the
> patch is 2 kb in size. :)

No problem, I will try to remember in the future. Some mailing lists 
prefer compressing patches because of the mangling that some mail list 
archiving software does to text attachments. I have trouble keeping 
track of which list prefers which format.

  parent reply	other threads:[~2010-06-02 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 14:26 configure patch for cross compilation Paul Bender
2010-06-02 14:57 ` Kay Sievers
2010-06-02 15:09 ` Paul Bender [this message]
2010-06-02 15:40 ` Kay Sievers

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=4C067422.5050607@san.rr.com \
    --to=pebender@san.rr.com \
    --cc=linux-hotplug@vger.kernel.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).