summaryrefslogtreecommitdiff
path: root/meta/recipes-core
diff options
context:
space:
mode:
authorHongxu Jia <hongxu.jia@windriver.com>2016-02-19 00:54:40 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-02-28 11:32:33 +0000
commitb806e4c004a7e10461fe7428fc130a5aa2528039 (patch)
treeff25ef035d6babb60d2423fd28f08ecf24757c18 /meta/recipes-core
parente469717d324b3aa29f165c7dc242c9d634be168f (diff)
downloadopenembedded-core-b806e4c004a7e10461fe7428fc130a5aa2528039.tar.gz
openembedded-core-b806e4c004a7e10461fe7428fc130a5aa2528039.tar.bz2
openembedded-core-b806e4c004a7e10461fe7428fc130a5aa2528039.zip
gcc: use relative path for configure script
The absolute path (/path/to/configure) caused __FILE__ to be an absolute path. If 'assert' invoked, it uses __FILE__, and build path would be in elf files. In assert.h ... .# define assert(expr) \ ((expr) \ ? __ASSERT_VOID_CAST (0) \ : __assert_fail (__STRING(expr), __FILE__, __LINE__, __ASSERT_FUNCTION)) ... Which triggered buildpaths QA issue: ... | libgcc-5.3.0: File work/core2-64-poky-linux/libgcc/5.3.0-r0/packages-split/ libgcc-dev/usr/lib64/x86_64-poky-linux/5.3.0/libgcc.a in package contained reference to tmpdir [buildpaths] ... Use relative path to run configure can fix the problem. [YOCTO #7058] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/recipes-core')
0 files changed, 0 insertions, 0 deletions