diff options
author | Robert Yang <liezhi.yang@windriver.com> | 2013-09-15 09:13:12 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-09-17 14:25:58 +0100 |
commit | 22ac874512c2c1213aae8e1644bd59050b37a63c (patch) | |
tree | c5d5772f1a9a36f45ec007eebadd0b3d17c9adb6 /meta/classes | |
parent | 4bcc087290661544dd5f6466d2d6ab74488f34ec (diff) | |
download | openembedded-core-22ac874512c2c1213aae8e1644bd59050b37a63c.tar.gz openembedded-core-22ac874512c2c1213aae8e1644bd59050b37a63c.tar.bz2 openembedded-core-22ac874512c2c1213aae8e1644bd59050b37a63c.zip |
coreutils: set acpaths to avoid "Argument list too long" error
There would be an error when the TMPDIR is long/deep, for example when
len(TMPDIR) = 350 while our supported longest value is 410:
[snip]
aclocal: error: cannot open xxx
autoreconf: aclocal failed with exit status: 1
ERROR: autoreconf execution failed.
[snip]
Let aclocal use the relative path for the m4 file rather than the
absolute would fix the problem.
Another fix is that we can modify autotools.bbclass to let it use the
relative path rather than the absolute, but I don't think that we have
to do that based on the following 2 thoughts:
* The coreutils is the only recipe which has this issue as far as we
know when len(TMPDIR) <= 410, because it has the most amount of m4
files (more than 400 ones).
* That would impact all the recipes which use autotools.bbclass, and we
are not sure about the side effect, for example, it would break the
build there is a sub-configure.
[YOCTO #2766]
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes')
0 files changed, 0 insertions, 0 deletions