From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] autotools.bbclass: update gnu-config files always
Date: Wed, 10 Oct 2012 12:55:19 +0200 [thread overview]
Message-ID: <50755417.3010001@linaro.org> (raw)
In-Reply-To: <1349822091.15658.196.camel@ted>
W dniu 10.10.2012 00:34, Richard Purdie pisze:
> On Tue, 2012-10-09 at 22:01 +0200, Marcin Juszkiewicz wrote:
>> + # not all recipes which use autotools use it's do_configure
>> + ( for ac in `find ${S} -name configure.in -o -name configure.ac`; do
>> + install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.guess `dirname $ac`
>> + install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.sub `dirname $ac`
>> + done )
> I'm not sure we want to go down this route. How about we mandate that
> everything call autotools_do_configure but allow various sections of it
> to be optional depending on some variables.
How would we support ncurses then? It runs configure in different ways
due to ENABLE_WIDEC variable (some play with EXTRA_OECONF maybe).
Or slang which has ${S}/autoconf/configure.ac when autotools.bbclass
checks only for ${S}/configure.{in,ac} when it decides to run autoreconf?
db one is easier as there we can add some variable like SKIP_AUTORECONF
and it should work. Similar with xinetd.
> We could then trigger the above behaviour for recipes which disable
> reautoconf?
That's an option. But we need also something for situations like
slang/ncurses.
> Ideally, we should be able to reautoconf everything and we shouldn't
> have exceptions at all.
And no reset for PARALLEL_MAKE as well. But we learnt during those OE
years that there is no such thing as ideal situation.
> The aim here is to make things more deterministic and make it clear
> which code paths are being used where and why.
Agree.
next prev parent reply other threads:[~2012-10-10 11:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 8:58 Best way to update gnu-config? Marcin Juszkiewicz
2012-09-18 9:00 ` [PATCH 1/2] ncurses: Update gnu-config files to version used by OE-Core Marcin Juszkiewicz
2012-09-18 9:00 ` [PATCH 2/2] db: " Marcin Juszkiewicz
2012-09-18 11:20 ` Burton, Ross
2012-09-18 11:43 ` Marcin Juszkiewicz
2012-09-18 10:40 ` [PATCH 1/2] ncurses: " Koen Kooi
2012-09-18 10:43 ` Marcin Juszkiewicz
2012-10-08 16:32 ` [PATCH 1/4] autotools.bbclass: update gnu-config files always Marcin Juszkiewicz
2012-10-09 4:38 ` Chris Larson
2012-10-09 20:01 ` [PATCH] " Marcin Juszkiewicz
2012-10-09 22:34 ` Richard Purdie
2012-10-10 10:55 ` Marcin Juszkiewicz [this message]
2012-09-18 9:08 ` Best way to update gnu-config? Richard Purdie
2012-09-18 9:29 ` Marcin Juszkiewicz
2012-09-18 10:36 ` Richard Purdie
2012-10-03 14:51 ` Marcin Juszkiewicz
2012-10-03 17:24 ` Michael Halstead
2012-10-03 17:25 ` Marcin Juszkiewicz
2012-10-08 16:24 ` [PATCH] gnu-config: update to 2012.08.14 to get support for AArch64 architecture Marcin Juszkiewicz
-- strict thread matches above, loose matches on Subject: below --
2012-10-03 9:51 Merging AArch64 support Marcin Juszkiewicz
2012-10-03 14:58 ` [PATCH] autotools.bbclass: update gnu-config files always Marcin Juszkiewicz
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=50755417.3010001@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=openembedded-core@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.