]> code.ossystems Code Review - openembedded-core.git/commit
python/python3: use cc_basename to replace CC for checking compiler
authorChangqing Li <changqing.li@windriver.com>
Tue, 23 Oct 2018 05:22:18 +0000 (13:22 +0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 3 Jan 2019 12:36:02 +0000 (12:36 +0000)
commit0bc0b83176117a7f10c9256aaae08553a116d45a
tree8758a14bb59e63bb46654c0825811cfed81e49f4
parente0db1beb6db624b3b743e780c298c63a1e177cfb
python/python3: use cc_basename to replace CC for checking compiler

When working path contains "clang"/"gcc"/"icc", it might be part of $CC
because of the "--sysroot" parameter. That could cause judgement error
about clang/gcc/icc compilers.

eg: if build under /yocto/builds/xicc/,  bitbake python,  $CC will contains
xicc, will make $CC match *icc, but actuall xicc just folder name.

When "*icc" is matched, below errors are reported when
compiling python/python3:
x86_64-wrs-linux-gcc: error: strict: No such file or directory
x86_64-wrs-linux-gcc: error: unrecognized command line option '-fp-model'

Here use cc_basename to replace CC for checking compiler to avoid such
kind of issue.

Signed-off-by: Li Zhou <li.zhou@windriver.com>
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-devtools/python/python/0001-python2-use-cc_basename-to-replace-CC-for-checking-c.patch [new file with mode: 0644]
meta/recipes-devtools/python/python3/0001-python3-use-cc_basename-to-replace-CC-for-checking-c.patch [new file with mode: 0644]
meta/recipes-devtools/python/python3_3.5.6.bb
meta/recipes-devtools/python/python_2.7.15.bb