On 2015-07-07 12:30 PM, Bruce Ashfield wrote: > On 2015-07-07 7:56 AM, Gorny Krystian wrote: >> Hi, >> >> I try to build an image for a x86 architecture with RT-Preemtp Patch. So >> I use the genericx86 machine and try to build the core-image-rt recipe. >> This fails with the following errors: >> >> /> ERROR: Nothing PROVIDES 'linux-yocto-rt' (but >> /media/disk/myYocto/poky/meta/recipes-rt/images/core-image-rt.bb DEPENDS >> on or otherwise requires it)/ >> >> /> ERROR: linux-yocto-rt was skipped: incompatible with machine >> genericx86 (not in COMPATIBLE_MACHINE)/ >> >> /> ERROR: Required build target 'core-image-rt' has no buildable >> providers./ >> >> /> Missing or unbuildable dependency chain was: ['core-image-rt', >> 'linux-yocto-rt']/ >> >> So I add the following parameter to my local.conf file: >> >> /> COMPATIBLE_MACHINE_genericx86 = "genericx86"/ >> >> /> COMPATIBLE_MACHINE_quilt-native = "genericx86"/ >> >> /> PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"/ >> >> But I get this error: >> >> /> ERROR: Task 80 >> (/media/disk/myYocto/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.14.bb, >> >> do_compile) failed with exit code '1'/ >> >> In the log.do_compile file I see: >> >> /> NOTE: make -j 4 bzImage CC=i686-poky-linux-gcc >> LD=i686-poky-linux-ld.bfd/ >> >> /> make[3]: Nothing to be done for `all'./ >> >> /> CHK include/config/kernel.release/ >> >> /> GEN >> /media/disk/myYocto/poky/build/tmp/work/genericx86-poky-linux/linux-yocto-rt/3.14.36+gitAUTOINC+a996d95104_3428de7103-r0/linux-genericx86preempt-$/ >> >> >> /> CHK include/generated/uapi/linux/version.h/ >> >> /> CHK include/generated/utsrelease.h/ >> >> /> HOSTCC scripts/conmakehash/ >> >> /> HOSTCC scripts/sortextable/ >> >> /> CC scripts/mod/empty.o/ >> >> /> >> /media/disk/myYocto/poky/build/tmp/work-shared/genericx86/kernel-source/scripts/mod/empty.c:1:0: >> >> error: code model 'kernel' not supported in the 32 bit >mode/ >> >> /> /* empty file to figure out endianness / word size *// >> >> /> ^/ >> >> /> >> /media/disk/myYocto/poky/build/tmp/work-shared/genericx86/kernel-source/scripts/mod/empty.c:1:0: >> >> sorry, unimplemented: 64-bit mode not compiled in/ >> >> /> make[4]: *** [scripts/mod/empty.o] Error 1/ >> >> /> make[4]: *** Waiting for unfinished jobs..../ >> >> /> HOSTCC scripts/mod/mk_elfconfig/ >> >> /> make[3]: *** [scripts/mod] Error 2/ >> >> /> make[3]: *** Waiting for unfinished jobs..../ >> >> /> make[2]: *** [scripts] Error 2/ >> >> /> make[1]: *** [sub-make] Error 2/ >> >> /> make: *** [all] Error 2/ >> >> /> ERROR: oe_runmake failed/ >> >> /> WARNING: exit code 1 from a shell command./ >> >> I already tried genericx86_64 machine and it’s still not working. Are >> the genericx86 machine incompatible with the core-image-rt recipy? If >> yes how can I build a x86 image with the RT patch? > > What you did should have worked, since we do map the genericx86 BSP onto > one of the configurations that supports preempt-rt. > > It looks like a compile error has crept in .. I'll start a build and see > if it is indeed broken at the moment (and then I can fix it). > Assuming you are building with yocto/poky, you need the following patch. (note: this is configure tested only). Since without this bbappend, we don't have genericx86 mapped to a valid linux-yocto BSP and commit hash. I'll be sending this change for merging into the project shortly. Cheers, Bruce > Bruce > >> >> Many Thanks >> >> >> _____________________________________________________________________ >> >> *Krystian Gorny* >> Research & Development >> >> Wipotec GmbH >> Adam-Hoffmann-Str. 26 >> 67657 Kaiserslautern >> >> T +49.631.34146-0 >> F +49.631.34146-8640 >> http://www.wipotec.com >> >> >> >> >> >> Legal information: >> Wipotec Wiege- und Positioniersysteme GmbH >> HRB 2317 Kaiserslautern, Management: T. Düppre, U. Wagner >> >> This e-mail may contain confidential and/or privileged information. >> If you are not the intended recipient (or have received this e-mail in >> error) >> please notify the sender immediately and delete this e-mail. Any >> unauthorized >> copying, disclosure or distribution of the material in this e-mail is >> strictly >> forbidden. >> >> >