From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Patches, Otavio Salvador <otavio@ossystems.com.br>,
about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] xkeyboard-config: this is architecture-indepedent, so set PACKAGE_ARCH
Date: Tue, 26 Feb 2013 11:43:55 -0800 [thread overview]
Message-ID: <1361907835.5119.57.camel@ted> (raw)
In-Reply-To: <CAJTo0Las-tCaN47Dz8Jn_W-YP6O__0Wqts3EBZDLbqAkv4F7FQ@mail.gmail.com>
On Tue, 2013-02-26 at 17:55 +0000, Burton, Ross wrote:
> On 26 February 2013 17:47, Otavio Salvador <otavio@ossystems.com.br> wrote:
> > If it changes the build depending in target and host, in the end it is
> > not architecture independant code.
>
> I think this is just autotools being nosy and failing when it doesn't
> know what "alllinux" is. The files don't change as they are literally
> just installed.
Check exactly what is in configure.ac. You should be able to use allarch
and if you can't, it means the configure script is referencing the
compiler, even if it shouldn't be using it. Its designed such that these
accesses fail verbosely. It should be a simple fix if the recipe really
is just configuration.
Using the allarch class is infinitely preferable as it gets the sstate
bits right.
Cheers,
Richard
next prev parent reply other threads:[~2013-02-26 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 12:36 [PATCH] xkeyboard-config: this is architecture-indepedent, so set PACKAGE_ARCH Ross Burton
2013-02-26 14:32 ` Otavio Salvador
2013-02-26 17:42 ` Burton, Ross
2013-02-26 17:47 ` Otavio Salvador
2013-02-26 17:55 ` Burton, Ross
2013-02-26 18:09 ` Otavio Salvador
2013-02-26 19:43 ` Richard Purdie [this message]
2013-02-26 20:44 ` Burton, Ross
2013-02-26 20:52 ` Otavio Salvador
2013-02-27 14:47 ` Burton, Ross
2013-03-01 0:10 ` Richard Purdie
2013-02-26 22:37 ` Martin Jansa
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=1361907835.5119.57.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=ross.burton@intel.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