On 24 October 2017 at 10:05, Manjukumar Matha <[email protected]> wrote: > On ZU+ machines, we set the default tune for the lib32 multilib > configuration.This allows users to select multilib by simply requiring > conf/multilib.conf in their build setups. > > Signed-off-by: Cyril Chemparathy <[email protected]> > Tested-by: Bhargava Sreekantappa Gayathri > <[email protected]> > Signed-off-by: Manjukumar Matha <[email protected]> > --- > conf/machine/include/machine-xilinx-default.inc | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/conf/machine/include/machine-xilinx-default.inc > b/conf/machine/include/machine-xilinx-default.inc > index 137f49e..38b7dd3 100644 > --- a/conf/machine/include/machine-xilinx-default.inc > +++ b/conf/machine/include/machine-xilinx-default.inc > @@ -41,3 +41,6 @@ XSERVER ?= " \ > > XSERVER_EXT ?= "" > XSERVER_EXT_zynqmp ?= "xf86-video-armsoc" > + > +# Support multilib on zynqmp > +DEFAULTTUNE_virtclass-multilib-lib32_zynqmp = "armv7vethf-neon-vfpv4"
So you had sent a very similar patch a few months back, I had commented then that it would be a good idea to have the DEFAULTTUNE_virtclass-multilib-lib32 set in tune-zynqmp.inc. Is there an issue with setting the DEFAULTTUNE that way? https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-June/002985.html Thanks, Nathan -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
