Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: wenzong.fan@windriver.com
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] autotools.bbclass: using relative paths for acpaths
Date: Thu, 27 Sep 2012 09:34:36 -0700	[thread overview]
Message-ID: <5064801C.1060906@linux.intel.com> (raw)
In-Reply-To: <cover.1348734058.git.wenzong.fan@windriver.com>

On 09/27/2012 01:23 AM, 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]
>
> The following changes since commit 0b09e50810162a07ef0aecee91ee32b4a36334a3:
>
>    busybox: Fix misplaced quote (2012-09-26 18:28:36 +0100)
>
> are available in the git repository at:
>
>    git://git.pokylinux.org/poky-contrib wenzong/2766
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/2766
>
> Wenzong Fan (1):
>    autotools.bbclass: using relative paths for acpaths
>
>   meta/classes/autotools.bbclass |    3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>

Merged into OE-Core

Thanks
	Sau!




      parent reply	other threads:[~2012-09-27 16:47 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
2012-09-27 16:34 ` Saul Wold [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=5064801C.1060906@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wenzong.fan@windriver.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