Christopher Larson 1fd9a16d2a 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>

2012-11-14 15:58:08 +00:00

..

bash-4.2

bash: fix mkbuiltins build failure

2012-11-14 15:58:08 +00:00

bash_3.2.48.bb

bash: Make it possible to run bash 3.2.48 instead of 4.2.

2012-09-24 11:30:30 +01:00

bash_4.2.bb

bash: fix mkbuiltins build failure

2012-11-14 15:58:08 +00:00

bash.inc

meta: remove redundant _FOR_BUILD variables

2012-11-12 13:36:37 +00:00