From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] bash-completion: remove allarch
Date: Tue, 11 Mar 2014 15:31:34 +0100 [thread overview]
Message-ID: <20140311143134.GF2137@jama> (raw)
In-Reply-To: <8672BB614B4CCA40A6B3BDD6FD82050B57548165@COSNADEXC13.usr.ingenico.loc>
[-- Attachment #1: Type: text/plain, Size: 2299 bytes --]
On Fri, Mar 07, 2014 at 08:41:21AM +0000, Matthieu CRAPET wrote:
> Hi,
>
> Does it mean that " allarch " is incompatible with "autotools" ? Is this true for all recipes?
No, autotools (the -native tools used by this bbclass) are OK, only
problem is when it tries to use CC (which is TUNE_PKGARCH specific).
There are even some recipes which are using autotools and were detecting
CC in configure.ac without any good reason, so they were patched to stop
doing this and to allow using allarch.
allarch.bbclass now resets couple variables to make sure that configure
will at fail if it tries to detect CC.
> -----Message d'origine-----
> De : openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] De la part de Martin Jansa
> Envoyé : jeudi 6 mars 2014 18:05
> À : openembedded-devel@lists.openembedded.org
> Objet : [oe] [meta-oe][PATCH] bash-completion: remove allarch
>
> * it has runtime dependency on TUNE_PKGARCH bash, so it cannot be allarch
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta-oe/recipes-support/bash-completion/bash-completion_2.0.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-oe/recipes-support/bash-completion/bash-completion_2.0.bb b/meta-oe/recipes-support/bash-completion/bash-completion_2.0.bb
> index ad7fd28..155fe90 100644
> --- a/meta-oe/recipes-support/bash-completion/bash-completion_2.0.bb
> +++ b/meta-oe/recipes-support/bash-completion/bash-completion_2.0.bb
> @@ -16,7 +16,7 @@ SRC_URI[sha256sum] = "e5a490a4301dfb228361bdca2ffca597958e47dd6056005ef9393a5852
>
> PARALLEL_MAKE = ""
>
> -inherit allarch autotools
> +inherit autotools
>
> do_install_append() {
> install -d ${D}${sysconfdir}/bash_completion.d/
> --
> 1.9.0
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-03-11 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 17:04 [meta-oe][PATCH] bash-completion: remove allarch Martin Jansa
2014-03-06 17:59 ` Paul Eggleton
2014-03-06 19:21 ` Martin Jansa
2014-03-07 10:09 ` [oe] " Paul Eggleton
2014-03-07 10:09 ` Paul Eggleton
2014-03-07 18:28 ` [oe] " Martin Jansa
2014-03-07 18:28 ` Martin Jansa
2014-03-15 16:01 ` [oe] " Martin Jansa
2014-03-15 16:01 ` Martin Jansa
2014-03-07 8:41 ` Matthieu CRAPET
2014-03-11 14:31 ` Martin Jansa [this message]
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=20140311143134.GF2137@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.