diff options
author | Christopher Larson <chris_larson@mentor.com> | 2012-11-14 07:55:09 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-11-14 15:58:08 +0000 |
commit | 1fd9a16d2a4594a4e9179dc7353ac51ce32eb712 (patch) | |
tree | bab1377bacffc78c8f7b775ea410517ec4e9106e /meta/recipes-extended/which | |
parent | aa75269454ebe7498e59fc2d6ca1fa43ce4b74bd (diff) | |
download | poky-1fd9a16d2a4594a4e9179dc7353ac51ce32eb712.tar.gz |
bash: fix mkbuiltins build failure
On hosts with FORTIFY_SOURCES, stringize support is required, as it's used by
the macros to wrap functions (e.g. read and open in unistd.h). Those wrappers
use the STRING() macro from unistd.h. A header in the bash sources overrides
the unistd.h macro to 'x' when HAVE_STRINGIZE is not defined, causing the
wrappers to generate calls to 'xread' and 'xopen', which do not exist,
resulting in a failure to link.
Assume we have stringize support when cross-compiling, which works around the
issue.
It may be best for upstream to either give up on supporting compilers without
stringize support, or to not define STRING() at all when FORTIFY_SOURCES is
defined, letting the unistd.h one be used, instead.
(From OE-Core rev: f7a25dd72d1d463eb72d48c6f9dd968d376496c0)
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended/which')
0 files changed, 0 insertions, 0 deletions