summaryrefslogtreecommitdiffstats
path: root/package/gcc
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2014-03-21 05:34:03 +0100
committerPeter Korsgaard <peter@korsgaard.com>2014-03-21 07:26:53 +0100
commitf4642eea7e5c0c375f1b892074a3c22637042deb (patch)
tree7ec2d4e54e32839e2fa74717878037438da77e97 /package/gcc
parenteb52ebc8bb5cdda9039da3992d813251068e2694 (diff)
downloadbuildroot-f4642eea7e5c0c375f1b892074a3c22637042deb.tar.gz
buildroot-f4642eea7e5c0c375f1b892074a3c22637042deb.zip
pkg-autotools: add a AUTOCONF_AC_CHECK_FILE_VAL macro
When configure.ac scripts do AC_CHECK_FILE tests, they always fail in cross-compilation contexts because it is not possible to check for file existence during the build process. Therefore we have to preseed the configure environment with ac_cv_file_<foo>=yes variable, <foo> being the path of the file, where all slashes, dots or dashes have been replaced by underscores. In the context of the boot-wrapper-aarch64, we will have to use three of these variables, with fairly complex paths. So instead of replicating the logic each time, we create a AUTOCONF_AC_CHECK_FILE_VAL macro to help defining such variables. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'package/gcc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud