On 03/12/2015 08:16 PM, Burton, Ross wrote:
On 12 March 2015 at 06:14, Robert Yang mailto:liezhi.y...@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 -
On Thu, 2015-03-12 at 12:16 +, Burton, Ross wrote:
> On 12 March 2015 at 06:14, Robert Yang
> 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?
>
On 12 March 2015 at 06:14, Robert Yang 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
From: Chong Lu
There would be an error when the TMPDIR is long/deep, for example when
len(TMPDIR) = 410 while our supported longest value is 410:
aclocal: error: cannot open xxx
autoreconf: aclocal failed with exit status: 1
ERROR: autoreconf execution failed.
Let aclocal use the re
ping
On 04/09/2014 05:44 PM, Chong Lu wrote:
There would be an error when the TMPDIR is long/deep, for example when
len(TMPDIR) = 410 while our supported longest value is 410:
aclocal: error: cannot open xxx
autoreconf: aclocal failed with exit status: 1
ERROR: autoreconf executi
ping
On 04/09/2014 05:44 PM, Chong Lu wrote:
There would be an error when the TMPDIR is long/deep, for example when
len(TMPDIR) = 410 while our supported longest value is 410:
aclocal: error: cannot open xxx
autoreconf: aclocal failed with exit status: 1
ERROR: autoreconf executi
There would be an error when the TMPDIR is long/deep, for example when
len(TMPDIR) = 410 while our supported longest value is 410:
aclocal: error: cannot open xxx
autoreconf: aclocal failed with exit status: 1
ERROR: autoreconf execution failed.
Let aclocal use the relative path for t
