Openembedded Core Discussions
 help / color / mirror / Atom feed
From: wenzong fan <wenzong.fan@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] autotools.bbclass: using relative paths for acpaths
Date: Fri, 28 Sep 2012 15:31:39 +0800	[thread overview]
Message-ID: <5065525B.7050206@windriver.com> (raw)
In-Reply-To: <1348765159.11186.11.camel@ted>

On 09/28/2012 12:59 AM, Richard Purdie wrote:
> On Thu, 2012-09-27 at 16:23 +0800, wenzong.fan@windriver.com wrote:
>> From: Wenzong Fan<wenzong.fan@windriver.com>
>>
>> Fix autotools.bbclass to use relative paths for acpaths instead of
>> absolute ones. Since absolute paths may cause potential autoreconf
>> error like:
>>
>>      Can't exec "/bin/sh": Argument list too long ...
>>
>> This error occurs while building coreutils with long TMPDIR, because
>> it has bunch of m4 files need to be expanded.
>>
>> [YOCTO #2766]
>>
>> Signed-off-by: Wenzong Fan<wenzong.fan@windriver.com>
>> ---
>>   meta/classes/autotools.bbclass |    3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/classes/autotools.bbclass b/meta/classes/autotools.bbclass
>> index e4e034b..874e01d 100644
>> --- a/meta/classes/autotools.bbclass
>> +++ b/meta/classes/autotools.bbclass
>> @@ -130,7 +130,8 @@ autotools_do_configure() {
>>   		if [ x"${acpaths}" = xdefault ]; then
>>   			acpaths=
>>   			for i in `find ${S} -maxdepth 2 -name \*.m4|grep -v 'aclocal.m4'| \
>> -				grep -v 'acinclude.m4' | sed -e 's,\(.*/\).*$,\1,'|sort -u`; do
>> +				grep -v 'acinclude.m4' | sed -e 's,\(.*/\).*$,\1,'|sort -u| \
>> +				sed -e 's,${S},\.,'`; do
>>   				acpaths="$acpaths -I $i"
>>   			done
>>   		else
>
> We applied this but it nearly instantly caused build failure reports.
> Anything with multiple configure.ac files where sub configures are used
> such as bdwgc-native will fail after this.
>
> I've therefore reverted it and we need to find another way.

Sorry, I didn't figure this out while building a sato image. If we can't 
make everything happy, could we get back the original ways which only 
fix it for coreutils?

With the limit to length of TMPDIR, this issue should rarely occurs.

Thanks
Wenzong

>
> Cheers,
>
> Richard
>
>



  reply	other threads:[~2012-09-28  7:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27  8:23 [PATCH 0/1] autotools.bbclass: using relative paths for acpaths wenzong.fan
2012-09-27  8:23 ` [PATCH 1/1] " wenzong.fan
2012-09-27 16:59   ` Richard Purdie
2012-09-28  7:31     ` wenzong fan [this message]
2012-09-27 16:34 ` [PATCH 0/1] " Saul Wold

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=5065525B.7050206@windriver.com \
    --to=wenzong.fan@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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