From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] tar: set acpaths to avoid "Argument list too long" error
Date: Thu, 12 Mar 2015 12:43:34 +0000 [thread overview]
Message-ID: <1426164214.9114.105.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0LbtbqvHgJG9i6zdY+YcBU70dHJhVFE=fBX=k46ty8N8=g@mail.gmail.com>
On Thu, 2015-03-12 at 12:16 +0000, Burton, Ross wrote:
> On 12 March 2015 at 06:14, Robert Yang <liezhi.yang@windriver.com>
> wrote:
> +acpaths = "-I ./m4"
>
> Why does this only happen on tar? Why is it safe to pass just -I ./m4
> when the detected list that you're overriding is effectively -I ./m4
> -I ./tests?
>
> Would it be better to just make all include paths relative to ${S}
> when generating the acpaths?
We tried that. Subconfigures break:
http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/classes/autotools.bbclass?id=3c58f92d46e32c40b80575f14e0f6f66c9920c66
Cheers,
Richard
next prev parent reply other threads:[~2015-03-12 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 6:14 [PATCH 0/1] tar: fix for len(TMPDIR) = 410 build Robert Yang
2015-03-12 6:14 ` [PATCH 1/1] tar: set acpaths to avoid "Argument list too long" error Robert Yang
2015-03-12 12:16 ` Burton, Ross
2015-03-12 12:43 ` Richard Purdie [this message]
2015-03-13 1:51 ` Robert Yang
-- strict thread matches above, loose matches on Subject: below --
2014-04-09 9:44 [PATCH 0/1] " Chong Lu
2014-04-09 9:44 ` [PATCH 1/1] " Chong Lu
2014-04-14 2:00 ` Chong Lu
2014-05-16 5:33 ` Chong Lu
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=1426164214.9114.105.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--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