Re: [yocto] Busybox_1.23.2 fails at do_compile on Poky-Sumo
Thanks for the the tip Raj. Here is the Build Config. Build Configuration: BB_VERSION = "1.37.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal-4.8" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "arm-cortex-a8" DISTRO = "poky" DISTRO_VERSION = "2.5" TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8" TARGET_FPU = "hard" meta-networking meta-python = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2" meta-userbsp-ti meta meta-poky meta-yocto-bsp meta-user-common = ":" meta-oe = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2" workspace= ":" Thanks! Mit freundlichen Grüßen / Best Regards, Dhanush On Thu, 18 Oct 2018 at 17:49, Khem Raj wrote: > Always send the Build Configuration that bitbake prints on top of > build. So someone can get some additional information about your build > to help you better. > On Thu, Oct 18, 2018 at 1:03 AM Dhanush K.S wrote: > > > > Hello Yocto, > > > > I'm currently building an image with the busybox_1.23.2.bb recipe > included, using Yocto Sumo 2.5 with the Bitbake version 1.37.0. It is > running on a CentOS host building images for the target ARM cortexa8. This > busybox recipe is placed in another custom layer. Though this recipe > compiles without errors in Poky-Fido, in Poky-Sumo I get compilation errors > due to missing header files. I have pasted a part of the log.do.compile > file with the error. > > > > # merged configuration written to .config (needs make) > > # > > NOTE: make -j 2 LD=arm-poky-linux-gnueabi-gcc -march=armv7-a -mfpu=neon > -mfloat-abi=hard -mcpu=cortex-a8 > --sysroot=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/recipe-sysroot > V=1 ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- SKIP_STRIP=y > busybox_unstripped > > rm -f .kernelrelease > > echo 1.23.2 > .kernelrelease > > > /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/gen_build_files.sh > /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2 > /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2 > > make -f > /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/Makefile > silentoldconfig > > make -f scripts/Makefile.build obj=scripts/basic > > > /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/gen_build_files.sh > /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2 > /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2 > > mkdir -p include > > make -f scripts/Makefile.build obj=scripts/kconfig silentoldconfig > > scripts/kconfig/conf -s Config.in > > # > > # using defaults found in .config > > # > > make -C > /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2 > KBUILD_SRC= .kernelrelease > > rm -f .kernelrelease > > echo 1.23.2 > .kernelrelease > > make -f scripts/Makefile.build obj=scripts/basic > > make -f scripts/Makefile.build obj=applets > > scripts/basic/split-include include/autoconf.h include/config > > gcc -Wp,-MD,applets/.usage.d -Wall -Wstrict-prototypes -O2 > -fomit-frame-pointer -Iinclude -Iinclude -o applets/usage > applets/usage.c > > gcc -Wp,-MD,applets/.applet_tables.d -Wall -Wstrict-prototypes -O2 > -fomit-frame-pointer -o applets/applet_tables applets/applet_tables.c > > > > /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/mkconfigs > include/bbconfigopts.h include/bbconfigopts_bz2.h > > make -f scripts/Makefile.build obj=scripts > > applets/usage_compressed include/usage_compressed.h applets > > applets/applet_tables include/applet_tables.h include/NUM_APPLETS.h > > gcc -Wp,-MD,applets/.usage_pod.d -Wall -Wstrict-prototypes -O2 > -fomit-frame-pointer -Iinclude -Iinclude -o applets/usage_pod > applets/usage_pod.c > > arm-poky-linux-gnueabi-gcc -Wp,-MD,applets/.applets.o.d -std=gnu99 > -Iinclude -Ilibbb -include include/autoconf.h -D_GNU_SOURCE -DNDEBUG > -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 > -D"BB_VER=KBUILD_STR(1.23.2)" -DBB_BT=AUTOCONF_TIMESTAMP -Wall -Wshadow > -Wwrite-strings -Wundef -Wstrict-prototypes -Wunused -Wunused
[yocto] Busybox_1.23.2 fails at do_compile on Poky-Sumo
Hello Yocto, I'm currently building an image with the busybox_1.23.2.bb recipe included, using Yocto Sumo 2.5 with the Bitbake version 1.37.0. It is running on a CentOS host building images for the target ARM cortexa8. This busybox recipe is placed in another custom layer. Though this recipe compiles without errors in Poky-Fido, in Poky-Sumo I get compilation errors due to missing header files. I have pasted a part of the log.do.compile file with the error. *# merged configuration written to .config (needs make)* *#* *NOTE: make -j 2 LD=arm-poky-linux-gnueabi-gcc -march=armv7-a -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8 --sysroot=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/recipe-sysroot V=1 ARCH=arm CROSS_COMPILE=arm-poky-linux-gnueabi- SKIP_STRIP=y busybox_unstripped* *rm -f .kernelrelease* *echo 1.23.2 > .kernelrelease* */opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/gen_build_files.sh /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2 /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2* *make -f /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/Makefile silentoldconfig* *make -f scripts/Makefile.build obj=scripts/basic* */opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/gen_build_files.sh /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2 /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2* *mkdir -p include* *make -f scripts/Makefile.build obj=scripts/kconfig silentoldconfig* *scripts/kconfig/conf -s Config.in* *#* *# using defaults found in .config* *#* *make -C /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2 KBUILD_SRC= .kernelrelease* *rm -f .kernelrelease* *echo 1.23.2 > .kernelrelease* *make -f scripts/Makefile.build obj=scripts/basic* *make -f scripts/Makefile.build obj=applets* * scripts/basic/split-include include/autoconf.h include/config* * gcc -Wp,-MD,applets/.usage.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -Iinclude -Iinclude -o applets/usage applets/usage.c * * gcc -Wp,-MD,applets/.applet_tables.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o applets/applet_tables applets/applet_tables.c * * /opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/busybox-1.23.2/scripts/mkconfigs include/bbconfigopts.h include/bbconfigopts_bz2.h* *make -f scripts/Makefile.build obj=scripts* * applets/usage_compressed include/usage_compressed.h applets* * applets/applet_tables include/applet_tables.h include/NUM_APPLETS.h* * gcc -Wp,-MD,applets/.usage_pod.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -Iinclude -Iinclude -o applets/usage_pod applets/usage_pod.c * * arm-poky-linux-gnueabi-gcc -Wp,-MD,applets/.applets.o.d -std=gnu99 -Iinclude -Ilibbb -include include/autoconf.h -D_GNU_SOURCE -DNDEBUG -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D"BB_VER=KBUILD_STR(1.23.2)" -DBB_BT=AUTOCONF_TIMESTAMP -Wall -Wshadow -Wwrite-strings -Wundef -Wstrict-prototypes -Wunused -Wunused-parameter -Wunused-function -Wunused-value -Wmissing-prototypes -Wmissing-declarations -Wno-format-security -Wdeclaration-after-statement -Wold-style-definition -fno-builtin-strlen -finline-limit=0 -fomit-frame-pointer -ffunction-sections -fdata-sections -fno-guess-branch-probability -funsigned-char -static-libgcc -falign-functions=1 -falign-jumps=1 -falign-labels=1 -falign-loops=1 -fno-unwind-tables -fno-asynchronous-unwind-tables -Os -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0=/usr/src/debug/busybox/1.23.2-r0 -fdebug-prefix-map=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/recipe-sysroot= -fdebug-prefix-map=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/busybox/1.23.2-r0/recipe-sysroot-native= -mtune=cortex-a8 -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/opt/ac500/yocto/branches/DEVEL_nextYocto/yocto/build_arm-cortex-a8/tmp/wo
[yocto] [opkg-utils PATCH] opkg-make-index: use ctime instead of mtime
From: Stefan Agner
When using sstate, two parallel builds can produce two packages
with the same mtime but different checksums. When later one of
those two builds fetches the others ipk, the package index does
not get udpated properly (since mtime matches). This ends up with
messages such as:
Downloading file:/../tmp/work/../image/...ipk.
Removing corrupt package file /../sysroot/../var/cache/opkg/volatile/...ipk
However, in that case, ctime is different. Use ctime instead of
mtime to prevent failures like this.
Suggested-by: Khem Raj
Signed-off-by: Stefan Agner
---
This addresses the issue discussed here:
http://lists.openembedded.org/pipermail/openembedded-core/2018-October/156348.html
opkg-make-index | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/opkg-make-index b/opkg-make-index
index 3227fc0..db7bf64 100755
--- a/opkg-make-index
+++ b/opkg-make-index
@@ -115,12 +115,12 @@ for abspath in files:
pkg = None
fnameStat = os.stat(abspath)
if filename in old_pkg_hash:
- if filename in pkgsStamps and int(fnameStat.st_mtime) ==
pkgsStamps[filename]:
+ if filename in pkgsStamps and int(fnameStat.st_ctime) ==
pkgsStamps[filename]:
if (verbose):
sys.stderr.write("Found %s in Packages\n" % (filename,))
pkg = old_pkg_hash[filename]
else:
- sys.stderr.write("Found %s in Packages, but mtime differs -
re-reading\n" % (filename,))
+ sys.stderr.write("Found %s in Packages, but ctime differs -
re-reading\n" % (filename,))
if not pkg:
if (verbose):
@@ -137,7 +137,7 @@ for abspath in files:
else:
old_filename = ""
s = packages.add_package(pkg, opt_a)
- pkgsStamps[filename] = fnameStat.st_mtime
+ pkgsStamps[filename] = fnameStat.st_ctime
if s == 0:
if old_filename:
# old package was displaced by newer
--
2.13.6
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] SUSE SLES target OS
Hello everyone, I need to get started on a Yocto set that will build a minimal core for a target OS of SUSE Linux Enterprise Server on x64 target hardware like a MinnowBoard. I have scoured the web, SUSE, and this list's (Yocto Project) archives, but have run into no pointers. My guess is that it is right under my nose that can be seen with more experience rather than being hidden behind private walls. Will someone please get me started on the pointers and downloads I need to get started? I have already run through a tutorial on creating a core OS using Yocto for a WandBoard target hardware. Thank you ! Joe -- -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SUSE SLES target OS
Do you mean OpenSuse? Since SLES is only build/provide to you by SUSE directly, it would be the same as trying to build your own RHEL instead of fedora. That would be difficult without theirs repositories ;-) Saludos / Regards / Mit Freundlichen grüßen / Atenciosamente Ismael Martínez Dibene > Am 19.10.2018 um 16:17 schrieb Joe Flowers : > > Hello everyone, > > I need to get started on a Yocto set that will build a minimal core for a > target OS of SUSE Linux Enterprise Server on x64 target hardware like a > MinnowBoard. > > I have scoured the web, SUSE, and this list's (Yocto Project) archives, but > have run into no pointers. My guess is that it is right under my nose that > can be seen with more experience rather than being hidden behind private > walls. > > Will someone please get me started on the pointers and downloads I need to > get started? > > I have already run through a tutorial on creating a core OS using Yocto for a > WandBoard target hardware. > > > Thank you ! > > Joe > -- > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-layer raspberry
Hello, Do you know if I include tha raspberrypi layer it would compile to a raspberry pi 1 machine as well or only to the later models? thanks, Zoli -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SUSE SLES target OS
On Fri, Oct 19, 2018 at 2:17 PM, Joe Flowers wrote: > Hello everyone, > > I need to get started on a Yocto set that will build a minimal core for a > target OS of SUSE Linux Enterprise Server on x64 target hardware like a > MinnowBoard. The Yocto project supports building distros based on OpenEmbedded. You can't use Yocto to build SUSE. (You can use Yocto to build an OpenEmbedded based distro on a SUSE host... but if I understand correctly, that's not what you're asking, right?). > I have scoured the web, SUSE, and this list's (Yocto Project) archives, but > have run into no pointers. My guess is that it is right under my nose that > can be seen with more experience rather than being hidden behind private > walls. > > Will someone please get me started on the pointers and downloads I need to > get started? > > I have already run through a tutorial on creating a core OS using Yocto for > a WandBoard target hardware. > > > Thank you ! > > Joe > -- > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SUSE SLES target OS
Yes, unfortunately, I mean SLES. Your answer implies that to create a minimal SLES build I will have to abandon Yocto and look for another build (or reduction) solution as I know this has been done by non-SUSE entities. On Fri, Oct 19, 2018 at 5:33 PM Ismael Martínez Dibene wrote: > Do you mean OpenSuse? Since SLES is only build/provide to you by SUSE > directly, it would be the same as trying to build your own RHEL instead of > fedora. That would be difficult without theirs repositories ;-) > > Saludos / Regards / Mit Freundlichen grüßen / Atenciosamente > Ismael Martínez Dibene > > > Am 19.10.2018 um 16:17 schrieb Joe Flowers : > > > > Hello everyone, > > > > I need to get started on a Yocto set that will build a minimal core for > a target OS of SUSE Linux Enterprise Server on x64 target hardware like a > MinnowBoard. > > > > I have scoured the web, SUSE, and this list's (Yocto Project) archives, > but have run into no pointers. My guess is that it is right under my nose > that can be seen with more experience rather than being hidden behind > private walls. > > > > Will someone please get me started on the pointers and downloads I need > to get started? > > > > I have already run through a tutorial on creating a core OS using Yocto > for a WandBoard target hardware. > > > > > > Thank you ! > > > > Joe > > -- > > > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-layer raspberry
Hi, On Fri, Oct 19, 2018 at 11:39 PM Zolee K wrote: > Hello, > > Do you know if I include tha raspberrypi layer it would compile to a > raspberry pi 1 machine as well or only to the later models? > > RaspberryPi 1 should work just fine. -- Andrei Gherzan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-layer raspberry
Cool, thanks! On 2018. Oct 20., Sat at 0:04, Andrei Gherzan wrote: > > Hi, > > On Fri, Oct 19, 2018 at 11:39 PM Zolee K > wrote: > >> Hello, >> >> Do you know if I include tha raspberrypi layer it would compile to a >> raspberry pi 1 machine as well or only to the later models? >> >> > RaspberryPi 1 should work just fine. > -- > Andrei Gherzan > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Python-tkinter
On Thu, Oct 4, 2018 at 4:09 PM nishant poorswani wrote: > Hey. I want to add python-tkinter into my image. > I've added in my local.conf . When I try to use it I cannot import Tkinter > into my code. Can anyone help with this? I get an error If this fails > Python may not be configured properly. ImportError: No module named > _tkinter. Any help would be appreciated. > -- The reason is that tk is not in oe-core (even though tcl is), so the _tkinter python extension (compiled c code) is disabled.[1] If you would file a bug [2] for this I’ll take a crack at a fix in 2.7 cycle as tkinter is useful for matlab that I’ve been working on. Component should be “core”. [1] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/python/python3/avoid_warning_about_tkinter.patch#n23 [2] https://bugzilla.yoctoproject.org/ > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
