you could use multilib add something like this below to local.conf require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "armv7at-neon”
> On Apr 26, 2016, at 10:53 PM, Jaggi, Manish <manish.ja...@caviumnetworks.com> > wrote: > > It worked, thanks!! > > But I couldnt find support to include multilibs say for 32bit and 64bit gcc. > There is a MULTILIB macro but I am not sure how to use it? > I think multilib recipes (bbfiles) are required, how to get them? > > > Regards, > Manish Jaggi > From: Burton, Ross <ross.bur...@intel.com <mailto:ross.bur...@intel.com>> > Sent: Tuesday, April 26, 2016 2:27:12 PM > To: Jaggi, Manish > Cc: yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> > Subject: Re: [yocto] aarch64-oe-linux/bin/ld: cannot find -lgcc . Adding > native build support for arm64/aarch64 in oe-rootfs. > > > On 26 April 2016 at 09:37, Jaggi, Manish <manish.ja...@caviumnetworks.com > <mailto:manish.ja...@caviumnetworks.com>> wrote: > IMAGE_INSTALL_append = "gcc" > IMAGE_INSTALL_append += " glibc" > IMAGE_INSTALL_append += " libgcc" > IMAGE_INSTALL_append += " binutils" > IMAGE_INSTALL_append += " gccmakedep" > > You left out the development headers and libraries required to actually link. > > IMAGE_FEATURES is a more efficient way of doing this. EXTRA_IMAGE_FEATURES > += "tools-sdk" will add gcc/cpp/make/etc, and "dev-pkgs" will ensure that all > of the -dev packages are installed on your image, so you can link against > anything you've installed. > > Ross > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> > https://lists.yoctoproject.org/listinfo/yocto > <https://lists.yoctoproject.org/listinfo/yocto>
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
