Thanks Mark and Chris. I applied the patch from Chris and was able to build for arm.
Also, as Mark said bitbake -e xen returned the following for the OVERRIDES with the aarch64. OVERRIDES="linux:aarch64:pn-xen:fvp:aarch64:poky:class-target:libc-glibc:forcevariable" Regards, Sathees On 17/04/2019, 13:37, "M. Asselstine" <[email protected]> wrote: On Tue, Apr 16, 2019 at 4:51 PM Christopher Clark <[email protected]> wrote: > > On Mon, Apr 15, 2019 at 6:47 PM M. Asselstine <[email protected]> wrote: > > On Mon, Apr 15, 2019 at 9:05 PM Sathees Balya <[email protected]> wrote: > > > Hi, > > > > > > The xen recipe has a hard dependency on dev86-native package (meta-virtualization/recipes-extended/xen/xen.inc). It does not allow us to build for aarch64 natively for Arm. At the moment, we have a workaround in the bbappend file for xen to remove the dependency. > > > > > > DEPENDS_remove = "dev86-native" > > > > > > Can the recipe be made generic so that both x86 and Arm can be built without the need for the above workaround? Thanks. > > > > I am not sure I am following you correctly. But I believe what you are > > looking for is to drop "dev86-native" from DEPENDS, where it is > > currently listed, and instead list it in something like > > > > DEPENDS_x86 = "dev86-native" > > > > in the xen.inc file. ie. make use of the overrides mechanism to only > > require it for x86 arch. Am I close? > > Suggest: replace the string 'dev86-native' within xen.inc's DEPENDS > definition with: > > ${@bb.utils.contains('XEN_TARGET_ARCH', 'x86_64', 'dev86-native', '', d)} Does XEN_TARGET_ARCH ever actually deviate from TARGET_ARCH? I do prefer using the overrides as it tends to be overall more clear to read, but the will work too. Sathees, there isn't much to the overrides, do a 'bitbake -e xen' and pipe the output to a file. Then search for "OVERRIDES" and you should find a list of override words, appending one of these words to a variable such as DEPENDS will only set the assignment if the override is present. Read a few tutorials and examine some examples and you should be able to sort it out rather quickly. MarkA > > which will toggle the requirement for the dev86-native tools based on > the target arch the hypervisor is being built for. > If that looks OK, I can send a patch on top of the 4.12 version uprev > that I just posted. > > Christopher > > > > > MarkA > > > > > > > > > > > > > > > > > Regards, > > > > > > Sathees > > > > > > IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. > > > -- > > > _______________________________________________ > > > meta-virtualization mailing list > > > [email protected] > > > https://lists.yoctoproject.org/listinfo/meta-virtualization > > -- > > _______________________________________________ > > meta-virtualization mailing list > > [email protected] > > https://lists.yoctoproject.org/listinfo/meta-virtualization IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- _______________________________________________ meta-virtualization mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-virtualization
