On Fri, 2020-08-07 at 08:34 -0400, Bruce Ashfield wrote:
> This needs to go to oe-core.
> 
> But see some comments below.
> 
> On Fri, Aug 7, 2020 at 5:26 AM <qiang.zh...@windriver.com> wrote:
> > From: Zhang Qiang <qiang.zh...@windriver.com>
> > 
> > When compiling xilinx-zynq board linux-kernel-dev(v5.8) if
> > "GCC_PLUGINS=y", The following error will appear:
> > 
> > "HOSTCXX -fPIC scripts/gcc-plugins/arm_ssp_per_task_plugin.o
> > fatal error: gmp.h: No such file or directory"
> > 
> > the GCC_PLUGINS depend on return result of gcc-plugin.sh execution
> > however in gcc-plugin.sh use HOSTCC to detect the feature of GNU
> > extension of gcc, this will result that HOSTCC can compile the file
> > successfully, but HOSTCXX is used in the actual compilation process.
> > 
> > Signed-off-by: Zhang Qiang <qiang.zh...@windriver.com>
> > ---
> >  meta/classes/kernel.bbclass | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> > index cf43a5d604..d7ac2dc421 100644
> > --- a/meta/classes/kernel.bbclass
> > +++ b/meta/classes/kernel.bbclass
> > @@ -212,6 +212,8 @@ UBOOT_LOADADDRESS ?= "${UBOOT_ENTRYPOINT}"
> >  KERNEL_EXTRA_ARGS ?= ""
> > 
> >  EXTRA_OEMAKE = " HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" 
> > HOSTCPP="${BUILD_CPP}""
> > +EXTRA_OEMAKE += " HOSTCXX="${BUILD_CXX} ${BUILD_CXXFLAGS} 
> > ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}""
> 
> It is fine if we now need to add HOSTCXX/BUILDCXX, but do not drop HOSTCC 
> /BUILD_CFLAGS while making that addition.

It took me a minute to realise but its appending in the second line so
the variable is set, then appended to...

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8938): 
https://lists.yoctoproject.org/g/linux-yocto/message/8938
Mute This Topic: https://lists.yoctoproject.org/mt/76045798/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to