Re: [Angstrom-devel] Angstrom 1.7: systemd-gnome-image fails
Best Regards Ulf Samuelsson > 2 okt 2015 kl. 08:36 skrev Koen Kooi <k...@dominion.thruhere.net>: > > >> Op 30 sep. 2015, om 09:55 heeft Ulf Samuelsson <angstrom-...@emagii.com> het >> volgende geschreven: >> >> I downloaded the latests setup scripts and tried to build >> 'systemd-gnome-image'. >> >> This fails since bluez5 is trying to install files which already exists. >> The preferred Bluetooth in Angstrom-1.7 is bluez4 so this is not surprising. > > > Ehm, there is not angstrom ‘1.7’, can you check the version again? > >> >> I built 'systemd-gnome-image' earlier this summer with success. >> >> The problem seems to be that in May, Khem Raj patched meta-photography >> so gvfs is dependent on bluez5, and in September Koen updated Angstrom >> to use the latest meta-photography. >> >> >> "meta-photography": >> -- >> commit 7be7ab65210842b6afb171638fb5b2e648d13a03 >> Author: Khem Raj <raj.k...@gmail.com> >> Date: Tue May 5 12:20:07 2015 -0700 >> >> gvfs: Depend on bluez5 since bluez4 is gone >> >> Signed-off-by: Khem Raj <raj.k...@gmail.com> >> -- >> >> Angstrom: >> -- >> commit 5e598c9f8efcbd3bc1418d7f06f4dafaec5896c3 >> Author: Koen Kooi <k...@dominion.thruhere.net> >> Date: Mon Sep 7 11:28:14 2015 +0200 >> >> layerman: bump meta-photography >> >> Signed-off-by: Koen Kooi <k...@dominion.thruhere.net> >> -- >> >> A short term solution is likely to revert Koen's patch, >> but long term, the meta-photography should be compatible with Angstrom. > > I have no idea what ‘compatible with angstrom’ means, can you explain? I think I did in the following sentence. > >> >> If that means moving Angstrom to bluez5 or changing meta-photography >> to support whatever the distro selects, I can't tell. >> >> BR >> Ulf Samuelsson >> >> ___ >> Angstrom-distro-devel mailing list >> Angstrom-distro-devel@linuxtogo.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel >> > > > ___ > Angstrom-distro-devel mailing list > Angstrom-distro-devel@linuxtogo.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Angstrom 1.7: systemd-gnome-image fails
Yocto-1.7 branch of course Best Regards Ulf Samuelsson > 2 okt 2015 kl. 08:36 skrev Koen Kooi <k...@dominion.thruhere.net>: > > >> Op 30 sep. 2015, om 09:55 heeft Ulf Samuelsson <angstrom-...@emagii.com> het >> volgende geschreven: >> >> I downloaded the latests setup scripts and tried to build >> 'systemd-gnome-image'. >> >> This fails since bluez5 is trying to install files which already exists. >> The preferred Bluetooth in Angstrom-1.7 is bluez4 so this is not surprising. > > > Ehm, there is not angstrom ‘1.7’, can you check the version again? > >> >> I built 'systemd-gnome-image' earlier this summer with success. >> >> The problem seems to be that in May, Khem Raj patched meta-photography >> so gvfs is dependent on bluez5, and in September Koen updated Angstrom >> to use the latest meta-photography. >> >> >> "meta-photography": >> -- >> commit 7be7ab65210842b6afb171638fb5b2e648d13a03 >> Author: Khem Raj <raj.k...@gmail.com> >> Date: Tue May 5 12:20:07 2015 -0700 >> >> gvfs: Depend on bluez5 since bluez4 is gone >> >> Signed-off-by: Khem Raj <raj.k...@gmail.com> >> -- >> >> Angstrom: >> -- >> commit 5e598c9f8efcbd3bc1418d7f06f4dafaec5896c3 >> Author: Koen Kooi <k...@dominion.thruhere.net> >> Date: Mon Sep 7 11:28:14 2015 +0200 >> >> layerman: bump meta-photography >> >> Signed-off-by: Koen Kooi <k...@dominion.thruhere.net> >> -- >> >> A short term solution is likely to revert Koen's patch, >> but long term, the meta-photography should be compatible with Angstrom. > > I have no idea what ‘compatible with angstrom’ means, can you explain? > >> >> If that means moving Angstrom to bluez5 or changing meta-photography >> to support whatever the distro selects, I can't tell. >> >> BR >> Ulf Samuelsson >> >> ___ >> Angstrom-distro-devel mailing list >> Angstrom-distro-devel@linuxtogo.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel >> > > > ___ > Angstrom-distro-devel mailing list > Angstrom-distro-devel@linuxtogo.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Angstrom 1.7: systemd-gnome-image fails
I downloaded the latests setup scripts and tried to build 'systemd-gnome-image'. This fails since bluez5 is trying to install files which already exists. The preferred Bluetooth in Angstrom-1.7 is bluez4 so this is not surprising. I built 'systemd-gnome-image' earlier this summer with success. The problem seems to be that in May, Khem Raj patched meta-photography so gvfs is dependent on bluez5, and in September Koen updated Angstrom to use the latest meta-photography. "meta-photography": -- commit 7be7ab65210842b6afb171638fb5b2e648d13a03 Author: Khem Raj <raj.k...@gmail.com> Date: Tue May 5 12:20:07 2015 -0700 gvfs: Depend on bluez5 since bluez4 is gone Signed-off-by: Khem Raj <raj.k...@gmail.com> -- Angstrom: -- commit 5e598c9f8efcbd3bc1418d7f06f4dafaec5896c3 Author: Koen Kooi <k...@dominion.thruhere.net> Date: Mon Sep 7 11:28:14 2015 +0200 layerman: bump meta-photography Signed-off-by: Koen Kooi <k...@dominion.thruhere.net> -- A short term solution is likely to revert Koen's patch, but long term, the meta-photography should be compatible with Angstrom. If that means moving Angstrom to bluez5 or changing meta-photography to support whatever the distro selects, I can't tell. BR Ulf Samuelsson ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] libepoxy_git.bb fails due to lack of EGL when building systemd-gnome-image
Might be a lack of dependency, will look into it. BR Ulf Samuelsson ulf@Hydra:~/Angstrom-1.7$ bitbake systemd-gnome-image NOTE: Started PRServer with DBfile: /home/ulf/Angstrom-1.7/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 37605, PID: 37317 Loading cache: 100% |#| ETA: 00:00:00 Loaded 3572 entries from dependency cache. Parsing recipes: 100% |###| Time: 00:01:15 Parsing of 2979 .bb files complete (2977 cached, 2 parsed). 3573 targets, 266 skipped, 0 masked, 0 errors. WARNING: No recipes available for: /home/ulf/Angstrom-1.7/sources/meta-raspberrypi/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.4.0.bbappend /home/ulf/Angstrom-1.7/sources/meta-fsl-arm/browser-layer/recipes-browser/chromium/chromium_40.0.2214.91.bbappend /home/ulf/Angstrom-1.7/sources/meta-kde4/recipes-misc-support/qt4-x11-free_4.8.5.bbappend /home/ulf/Angstrom-1.7/sources/meta-atmel/recipes-qt/qt4/qt4-embedded_4.8.5.bbappend /home/ulf/Angstrom-1.7/sources/meta-kde4/recipes-misc-support/qt4-native_4.8.5.bbappend WARNING: No bb files matched BBFILE_PATTERN_meta-dominion '^/home/ulf/Angstrom-1.7/sources/meta-dominion/' NOTE: Resolving any missing task queue dependencies NOTE: multiple providers are available for glibc (glibc, external-linaro-toolchain) NOTE: consider defining a PREFERRED_PROVIDER entry to match glibc NOTE: multiple providers are available for virtual/fftw (fftw, fftwl, fftwf) NOTE: consider defining a PREFERRED_PROVIDER entry to match virtual/fftw Build Configuration: BB_VERSION= 1.24.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-12.04 TARGET_SYS= arm-angstrom-linux-gnueabi MACHINE = beaglebone DISTRO= angstrom DISTRO_VERSION= v2014.12 TUNE_FEATURES = arm armv7a vfp thumb neon callconvention-hard TARGET_FPU= vfp-neon meta-angstrom = angstrom-v2014.12-yocto1.7:9575a7327c2b61e2d0b772da65caf640f7c8c6a7 meta-oe meta-efl meta-gpe meta-gnome meta-xfce meta-initramfs toolchain-layer meta-multimedia meta-networking meta-webserver meta-ruby meta-filesystems meta-perl meta-python = dizzy:2ebb8752f378c9987b0ece5a14915d703b872c1d meta-kde4 = master:f45abfd4d87b0132a2565499392d2d49f465d847 meta-java = master:d2b75b615e4612f9fa05950c1d76d4a719e573d4 meta-browser = master:1ed7500cc43706165ccac8daccba47124e63d3eb meta-mono = master:e8c390589dd83659506564c448d086b4f3d13666 meta-qt5 = master:478fe949a957471a4d20450f6e9375fe1d628591 meta-systemd = dizzy:2ebb8752f378c9987b0ece5a14915d703b872c1d meta-ros = master:37c6fd01ddfe862ec6af7a4c2d24b51d9d1cdd55 meta-uav = master:edf32a392b55a4267e6b072776e2aab6c8f7617e meta-telephony= master:65238f85305f3179491e5e4be8152ea35454ac84 meta-beagleboard-extras = dizzy:01ffda08de8f0bdff95fe76509e9aea8c6b49bfd meta-photography = master:b4cc4768b39610cc7fbb424e82a217d7e86fa25f meta-ci = master:6440090ec889f0c9363b8ee9ad76e2477071b734 meta-intel-iot-middleware = master:48604925ea011b6dba2953b407aff0fce5e7cbbb common-bsp= dizzy:01ffda08de8f0bdff95fe76509e9aea8c6b49bfd meta-ti = master:129783a9cba7902feb7f35d390b37d96b733a201 meta-fsl-arm = dizzy:db1571f40c375a398a8cdbb42de4c4f272ab0cd1 meta-fsl-arm-extra = dizzy:137645f5daf596c8630cf505b789bc2f174f1b1d meta-nslu2= master:ddf38dba9426b4a2047679e936521a5b1b06653e meta-htc meta-nokia meta-openmoko meta-palm = master:04eb33be364d5dad05a8c127fc3b62af9b34ab19 meta-handheld = master:57044c88e22443f312fe812cc481449c0110f2ef meta-intel meta-sugarbay meta-crownbay meta-emenlow meta-fri2 meta-jasperforest = dizzy:c39a4bf4450845fca6f1b26ccfc0db192a4567e8 meta-sunxi= master:715f2ace5bfe597ad93f3eec13d46f753023d8f0 meta-raspberrypi = master:6b63f6fcbdbde1694d55e314b86fadaa74dc858a meta-minnow = master:13a5f2ab84c7284647a3e067a33109c11dae0568 meta-dominion = dizzy:43741f26e100a8c228d10902963f079c3a167f24 meta-atmel= angstromv2014.12-staging:7b695a7297d257f9e26d87b02787ec9a2f570473 meta-exynos = master:f8395cd1c7f94938e292592d6f5d66efa64a meta-gumstix-community = master:d2017d3efe8d63940ec6aa33cd6e102e2d39dfc5 meta-qualcomm = master:1c876ee4dc5cb66d26d960f5b58c958ada2452a1 meta-edison = master:bcfe06e72158ec3b84279a27b4a5db9c9c50f5d3 meta-96boards = dizzy:9de69696ad228e31417090d04f1f5fed689f2029 meta-linaro meta-linaro-toolchain meta-aarch64 = dizzy:59655ebd6e10d9f4db4c2d63c7fac606779d meta = dizzy:7bd0c0576da1e595f37c0bb70c0d286b78a62eb0 NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: Failed to fetch URL ftp://pkg-isocodes.alioth.debian.org/pub/pkg-isocodes/iso-codes-1.4.tar.bz2, attempting MIRRORS if available WARNING
Re: [Angstrom-devel] Creating a flashing image for Beaglebone Black
Thanks, I already found those scripts. They are all to be added to the rootfs in the build directory. What I am looking for is a recipe/shell script that does this automatically, as well as adding the update as a systemd service (found an emmc.service file) Or was it all done manually? Best Regards Ulf Samuelsson u...@emagii.com +46 (722) 427 437 26 feb 2014 kl. 03:55 skrev Khem Raj raj.k...@gmail.com: On Feb 25, 2014, at 6:51 PM, Robert Nelson robertcnel...@gmail.com wrote: Might be a little bit-rotten, but the scripts are here: https://github.com/beagleboard/meta-beagleboard/tree/master/contrib/bone-flash-tool Never used them personally, just referenced them when creating the new debian based beagleboard.org image. Regards, use https://github.com/beagleboard/meta-beagleboard/tree/master/contrib/bone-flash-tool thats maintained. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Creating a flashing image for Beaglebone Black
Using Angstrom Distribution 1.4 for Beglebone Black. Some of the demos are available in an emmc flashing image which will upgrade the internal flash. Is there a script which will generate such an image, which I can download? BR Ulf Samuelsson ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Creating a flashing image for Beaglebone Black
2014-02-25 18:25, Chris Morgan skrev: On Tue, Feb 25, 2014 at 12:18 PM, Ulf Samuelsson angstrom-...@emagii.com wrote: Using Angstrom Distribution 1.4 for Beglebone Black. Some of the demos are available in an emmc flashing image which will upgrade the internal flash. Is there a script which will generate such an image, which I can download? BR Ulf Samuelsson I've found this: http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SetupmicroSD/SDcard This link does not work As well as this post: https://groups.google.com/forum/#!searchin/beagleboard/ubi/beagleboard/rfjXm2VKBwM/-FnLShKqVfEJ And this partitions an SD card, and adds a ubi file system. But I've had the same question about how to generate the sdcard emmc flashing image. I'd love to be pointed to better resources for this. Chris Most of the neccessary files, seems to be in meta-ti/contrib, but emmc.service is nowhere to be found inside meta-ti. Found something on the web, but no recipe to create a flashing image. Maybe this is done in a multistage operation, where the image is first copied to an SD-card, and then the contrib files are copied to the build directory together with MLO, u-boot.img and the rootfs BR Ulf Samuelsson ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Build error with latest sources in wp_block.c
This problem may be caused by a long path. Try installing directly in you home directory. Best Regards Ulf Samuelsson 21 jan 2014 kl. 19:58 skrev Andrei Radulescu-Banu andrei.radulescu-b...@exfo.com: Hi Khem, thanks for looking at this. I'm using Fedora release 17, bash version 4.2.39(1). Here is my /usr/include/linux/limits.h. Thanks, Andrei #ifndef _LINUX_LIMITS_H #define _LINUX_LIMITS_H #define NR_OPEN 1024 #define NGROUPS_MAX65536/* supplemental group IDs are available */ #define ARG_MAX 131072/* # bytes of args + environ for exec() */ #define LINK_MAX 127/* # links a file may have */ #define MAX_CANON255/* size of the canonical input queue */ #define MAX_INPUT255/* size of the type-ahead buffer */ #define NAME_MAX 255/* # chars in a file name */ #define PATH_MAX4096/* # chars in a path name including nul */ #define PIPE_BUF4096/* # bytes in atomic write to a pipe */ #define XATTR_NAME_MAX 255/* # chars in an extended attribute name */ #define XATTR_SIZE_MAX 65536/* size of an extended attribute value (64k) */ #define XATTR_LIST_MAX 65536/* size of extended attribute namelist (64k) */ #define RTSIG_MAX 32 #endif -Original Message- From: Khem Raj [mailto:raj.k...@gmail.com] Sent: Tuesday, January 21, 2014 1:23 PM To: angstrom-distro-devel@linuxtogo.org Cc: Andrei Radulescu-Banu Subject: Re: [Angstrom-devel] Build error with latest sources in wp_block.c On Monday, January 20, 2014 04:03:45 PM Andrei Radulescu-Banu wrote: enssl/crypto/whrlpool/wp_block.o ../deps/openssl/openssl/crypto/whrlpool/wp_block.c make[1]: execvp: printf: Argument list too long what is your host OS distribution and default shell ? and whats value of ARG_MAX declared in /include/linux/limits.h -- -Khem ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] builting Angstrom for beagleboard Xm with Qt5
2014-01-19 16:36, Aline Guisky skrev: So which image will contain qt5? I am not sure there are any recipes for such an image. You just have to search. Here are all the images in Angstrom (1.5) ./meta-smartphone/meta-fso/recipes-freesmartphone/images/fso2-console-image.bb ./meta-smartphone/meta-aurora/recipes-aurora/images/aurora-image.bb ./meta-smartphone/meta-android/recipes-core/images/chroot-image.bb ./meta-smartphone/meta-shr/recipes-shr/images/shr-image.bb ./meta-smartphone/meta-shr/recipes-shr/images/shr-lite-image.bb ./meta-angstrom/recipes-images/angstrom/systemd-gnome-image.bb ./meta-angstrom/recipes-images/angstrom/efl-nodm-image.bb ./meta-angstrom/recipes-images/angstrom/hardware-bringup-image.bb ./meta-angstrom/recipes-images/angstrom/development-gnome-image.bb ./meta-angstrom/recipes-images/angstrom/xfce-nm-image.bb ./meta-angstrom/recipes-images/angstrom/console-base-image.bb ./meta-angstrom/recipes-images/angstrom/systemd-image.bb ./meta-angstrom/recipes-images/angstrom/console-image.bb ./meta-openembedded/meta-initramfs/recipes-bsp/images/initramfs-kexecboot-image.bb ./meta-openembedded/meta-initramfs/recipes-bsp/images/initramfs-kexecboot-klibc-image.bb ./meta-kde/recipes-packagegroups/packagegroup-kde-image.bb ./meta-kde/recipes-images/plasma-desktop-image.bb ./meta-kde/recipes-images/angstrom-kde-desktop-image.bb ./meta-kde/recipes-images/angstrom-kde-active-image.bb ./meta-kde/recipes-images/plasma-active-image.bb ./meta-ettus/recipes/images/console-gnuradio-image.bb ./meta-ettus/recipes/images/console-openbts-devel-image.bb ./meta-ettus/recipes/images/hw-test-image.bb ./meta-ettus/recipes/images/console-e1xx-devel-image.bb ./meta-ettus/recipes/images/gnome-qt-image.bb ./meta-ettus/recipes/images/console-base-image.bb ./meta-ettus/recipes/images/gnome-gnuradio-image.bb ./meta-ettus/recipes/images/xfce-gnuradio-image.bb ./meta-ettus/recipes/images/systemd-openssh-image.bb ./meta-opie/recipes-opie/images/opie-xqtlauncher-image.bb ./meta-opie/recipes-opie/images/opie-kdepim-image.bb ./meta-opie/recipes-opie/images/opie-image.bb ./meta-beagleboard/meta-beagleboard-extras/recipes-images/cloud9/cloud9-gfx-image.bb ./meta-beagleboard/meta-beagleboard-extras/recipes-images/cloud9/cloud9-image.bb ./meta-beagleboard/meta-beagleboard-extras/recipes-images/cloud9/cloud9-gnome-image.bb ./meta-beagleboard/meta-beagleboard-extras/recipes-images/base/ti-hw-bringup-image.bb ./meta-raspberrypi/recipes-core/images/rpi-hwup-image.bb ./meta-raspberrypi/recipes-core/images/rpi-basic-image.bb ./meta-nslu2/classes/nslu2-image.bbclass ./meta-nslu2/recipes-bsp/slugimage/slugimage.bb ./meta-ti/classes/sdcard_image.bbclass ./meta-ti/recipes-misc/images/ti-hw-bringup-image.bb ./openembedded-core/meta/classes/core-image.bbclass ./openembedded-core/meta/classes/testimage.bbclass ./openembedded-core/meta/classes/image.bbclass ./openembedded-core/meta/recipes-qt/images/qt4e-demo-image.bb ./openembedded-core/meta-hob/recipes-core/images/hob-image.bb ./meta-java/recipes-images/images/java-test-image.bb You may want to look at: ./openembedded-core/meta/recipes-qt/images/qt4e-demo-image.bb and adapt it after your needs. BR Ulf On Jan 19, 2014, at 17:20, Ulf Samuelsson angstrom-...@emagii.com mailto:angstrom-...@emagii.com wrote: You have to build the right image. console-image does not contain Qt. Best Regards Ulf Samuelsson 20 jan 2014 kl. 11:59 skrev Aline Guisky ali...@linux4biz.com mailto:ali...@linux4biz.com: Hi, I'm an Angstrom and embedded newbie, and I hope someone can help me. Currently I've compiled an angstrom image using bitbake. I've have a kernel and u-boot image in my deploy directory and after executing: MACHINE=beagleboard ./oebb.sh bitbake console-image I also have a tarboll file system as well ( Angstrom-console-image-eglibc-ipk-v2012.12-beagleboard.rootfs.tar.bz2) but I was wondering, as I understand the path to a file system: build/tmp-angstrom_v2012_12-eglibc/sysroots/beagleboard/ but it is an incomplete file system... It's important because I have also compiled QT5 and I need openGl libs for multimedia support and I have libraries missing when executing my Qt example. to get the openGl libs for the Qt compilation (which completed successfully) I've executed: MACHINE=beagleboard ./oebb.sh bitbake libgles-omap3 Thanks for any help, Aline. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org mailto:Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] builting Angstrom for beagleboard Xm with Qt5
You have to build the right image. console-image does not contain Qt. Best Regards Ulf Samuelsson 20 jan 2014 kl. 11:59 skrev Aline Guisky ali...@linux4biz.com: Hi, I'm an Angstrom and embedded newbie, and I hope someone can help me. Currently I've compiled an angstrom image using bitbake. I've have a kernel and u-boot image in my deploy directory and after executing: MACHINE=beagleboard ./oebb.sh bitbake console-image I also have a tarboll file system as well ( Angstrom-console-image-eglibc-ipk-v2012.12-beagleboard.rootfs.tar.bz2) but I was wondering, as I understand the path to a file system: build/tmp-angstrom_v2012_12-eglibc/sysroots/beagleboard/ but it is an incomplete file system... It's important because I have also compiled QT5 and I need openGl libs for multimedia support and I have libraries missing when executing my Qt example. to get the openGl libs for the Qt compilation (which completed successfully) I've executed: MACHINE=beagleboard ./oebb.sh bitbake libgles-omap3 Thanks for any help, Aline. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] U-Boot in meta-ti is broken
It looks like the some of the u-boot recipes in meta-ti are broken. They do not include COMPATIBLE_MACHINE statements, so when building u-boot for non-ti machines, this recipe is choosen instead. This includes the u-boot 13.01 recipe BR ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] U-Boot in meta-ti is broken
2014-01-17 20:10, Philip Balister skrev: On 01/17/2014 02:00 PM, Ulf Samuelsson wrote: It looks like the some of the u-boot recipes in meta-ti are broken. They do not include COMPATIBLE_MACHINE statements, so when building u-boot for non-ti machines, this recipe is choosen instead. This includes the u-boot 13.01 recipe Should this email be o nthe meta-ti list? Philip layers.txt contains: meta-ti,git://github.com/Angstrom-distribution/meta-ti.git,angstrom-staging-yocto1.5,HEAD so Angstrom uses a local copy. * meta-angstrom * meta-openembedded * meta-ti all use local copies of the original layer Have run into the same problem for other things, where is it fixed in the original but not in the Angstrom version so it must be fixed in the Angstrom version. Maybe skipping the local copy is a good idea. BR Ulf BR ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Question about syslog replacement
You email is not really clear. You say that you need rsyslog, and then you ask how to get rid of it. Busybox has a configuration file to define what is included. Did you try to modify this? Best Regards Ulf Samuelsson 13 dec 2013 kl. 18:10 skrev Grzegorz Sikorski g.sikor...@kelvatek.com: Hi, I am using v2012.12 version of distro. I need to simply replace busybox-syslog by rsyslog. I have built everything, but cannot completely get rid of busybox-syslog from final filesystem and this is causing some issues. Is there any simple way to tell Angstrom that I do not want to use rsyslog as syslog daemon instead of busybox-syslog? I saw this thread http://lists.openembedded.org/pipermail/openembedded-devel/2010-May/064882.html, but I do not think it is embedded to Angstrom, is it? Thanks, Greg -- Asylia ExchangeDefender Message Security: Click below to verify authenticity http://www.exchangedefender.com/verify.asp?id=rBDHASoN021999from=g.sikor...@camlintechnologies.com ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] xfconf-4.10.0.bb fails on Ubuntu 12.04 LTS (x64) , maybe due to not depending on perl...
2013-12-07 01:29, Khem Raj skrev:
On Fri, Dec 6, 2013 at 2:53 PM, Ulf Samuelsson openembed...@emagii.com wrote:
recipes-xfce/xfconf/xfconf_4.10.0.bbappend:
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
EXTRA_OECONF = --disable-perl-bindings
This also results in xfconf-perl/Makefile.perl not beeing run,
and then the build completes.
I am going to try to make xfconf depend on perl instead.
Then hopefully, configure should find the perl for ARM
instead of the native perl.
You have to make sure that xfconf has proper cross tests when poking
for system capability like that. which is the real problem
here since its probablt trying to execute checks, if you point it to
target perl that will only be helpful if the execution bits somehow
can figure out the target perl capability.
The fix above to disable perl bindings is a good one since it provided
consistency even though at the expense of disabling a feature.
I did the following changes:
+PR = r1
+EXTRA_OE_CONF += PERL=${STAGING_DIR_TARGET}/usr/bin/perl
+EXTRA_OE_CONF += --with-sysroot=yes
(autotools uses lt_sysroot=`CC --print-sysroot`)
and then the build completes.
Also added a patch I saw checked in somewhere, but that is not related
to this problem.
--
Best Regards
Ulf Samuelsson
u...@emagii.com
+46 722 427437
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] xfconf-4.10.0.bb fails on Ubuntu 12.04 LTS (x64) , maybe due to not depending on perl...
Running Angstrom Master (Yocto-1.3) and building for beaglebone.
Have been using Ubuntu 12-04 LTS (i686) without problems.
Then I reinstalled the machine with Ubuntu 12-04 LTS (x64)
and then the build fails due to xfconf-4.10.0.bb
Have googled around without finding a solution, only a workaround,
This happens when making xfconf/xfconf-perl/Makefile.perl
In the linker phase, the linker does not find
libxconf-gvaluefuncs.a and libxfconf-0
/usr/bin/ld:cannot find -lxfconf-0
/usr/bin/ld:cannot find -l-ldbus-glib-1.
/usr/bin/ld:cannot find -l-ldbus-1
They find such libraries but they are skipped, due to incompatibility.
/usr/bin/ld: skipping incompatible
xfconf-perl/../xfconf/.libs/libxfconf-gvaluefuncs.a
same for -lxfconf
I think the error is because the build uses the native (x64) linker
instead of the ARM linker,
The libraries found are of course built for 32 bit ARM, thus not useable
and the linker
looks for something else.
This was interesting, since I have another machine which also
runs Ubuntu-12.04 LTS (x64) and on that machine,
the build completes without problem.
It turns out, that xfconf configure does not find any perl in the
openembedded sysroot, but finds /usr/bin/perl, the native perl.
I think that based on that, it decides to use the native linker.
In the first machine (failing), it continues and looks for some perl
modules.
checking for perl modules: ExtUtils::Depends, ExtUtils::PkgConfig,
Glib... yes,
On the second machine, this check fails.
checking for perl modules: ExtUtils::Depends, ExtUtils::PkgConfig,
Glib... no
*** Required perl modules not found to build perl bindings. Requirements
are:
***
*** ExtUtils::Depends0.300
*** ExtUtils::PkgConfig 1.000
*** Glib 1.020
***
Therefore configure decides to build xfconf without perl support, and thus
xfconf-perl/Makefile.perl does not get generated, removing the cause
of the failing build.
Googling for the problem, I found a guy on the gumstix mailing list
(Charles Ash ashchar...@gmail.com) which has a workaroung.
recipes-xfce/xfconf/xfconf_4.10.0.bbappend:
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
EXTRA_OECONF = --disable-perl-bindings
This also results in xfconf-perl/Makefile.perl not beeing run,
and then the build completes.
I am going to try to make xfconf depend on perl instead.
Then hopefully, configure should find the perl for ARM
instead of the native perl.
--
Best Regards
Ulf Samuelsson
u...@emagii.com
+46 722 427437
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] xfconf-4.10.0.bb fails on Ubuntu 12.04 LTS (x64) , maybe due to not depending on perl...
2013-12-07 00:14, Ash Charles skrev:
On Dec 6, 2013 11:53 PM, Ulf Samuelsson openembed...@emagii.com
mailto:openembed...@emagii.com wrote:
Running Angstrom Master (Yocto-1.3) and building for beaglebone.
Have been using Ubuntu 12-04 LTS (i686) without problems.
Then I reinstalled the machine with Ubuntu 12-04 LTS (x64)
and then the build fails due to xfconf-4.10.0.bb
http://xfconf-4.10.0.bb
Have googled around without finding a solution, only a workaround,
This happens when making xfconf/xfconf-perl/Makefile.perl
In the linker phase, the linker does not find
libxconf-gvaluefuncs.a and libxfconf-0
/usr/bin/ld:cannot find -lxfconf-0
/usr/bin/ld:cannot find -l-ldbus-glib-1.
/usr/bin/ld:cannot find -l-ldbus-1
They find such libraries but they are skipped, due to incompatibility.
/usr/bin/ld: skipping incompatible
xfconf-perl/../xfconf/.libs/libxfconf-gvaluefuncs.a
same for -lxfconf
I think the error is because the build uses the native (x64) linker
instead of the ARM linker,
The libraries found are of course built for 32 bit ARM, thus not
useable and the linker
looks for something else.
This was interesting, since I have another machine which also
runs Ubuntu-12.04 LTS (x64) and on that machine,
the build completes without problem.
It turns out, that xfconf configure does not find any perl in the
openembedded sysroot, but finds /usr/bin/perl, the native perl.
I think that based on that, it decides to use the native linker.
In the first machine (failing), it continues and looks for some
perl modules.
checking for perl modules: ExtUtils::Depends, ExtUtils::PkgConfig,
Glib... yes,
On the second machine, this check fails.
checking for perl modules: ExtUtils::Depends, ExtUtils::PkgConfig,
Glib... no
*** Required perl modules not found to build perl bindings.
Requirements are:
***
*** ExtUtils::Depends0.300
*** ExtUtils::PkgConfig 1.000
*** Glib 1.020
***
Therefore configure decides to build xfconf without perl support,
and thus
xfconf-perl/Makefile.perl does not get generated, removing the cause
of the failing build.
Googling for the problem, I found a guy on the gumstix mailing list
(Charles Ash ashchar...@gmail.com mailto:ashchar...@gmail.com)
which has a workaroung.
recipes-xfce/xfconf/xfconf_4.10.0.bbappend:
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
EXTRA_OECONF = --disable-perl-bindings
This also results in xfconf-perl/Makefile.perl not beeing run,
and then the build completes.
I am going to try to make xfconf depend on perl instead.
Then hopefully, configure should find the perl for ARM
instead of the native perl.
That makes more sense than my little hack disabling perl bindings.
I'll give this approach a try.
-- Ash
I tried it, but it didnt work.
configure.ac contains
AC_PATH_PROGS([PERL], [perl5.8 perl5.6 perl5 perl])
which is looking for
perl5.8
perl5.6
perl5
perl
Angstrom-1.3 build perl-5.14.2 so only the last check have a chance.
AC_PATH_PROGS searches for the first in the argument 2 list, which
can be found in the current PATH.
When I look at the run.do_configure.* of xfconf, the PATH contains
build/sysroots/x86_64/usr/... and
/usr/bin
but it does not contain
build/sysroots/beaglebone/usr/bin
which is needed to find the ARM perl.
Have no clue why.
There is already a dependency on perl-native in the recipe.
I tried replaced it with dependency on perl,
but I still get the host PATH and not the target PATH.
I noticed that xfconf configure does not understand
--with-libtool-sysroot=
added
EXTRA_OECONF += --with-sysroot=${STAGING_DIR_TARGET}
to no avail.
The tree in question was initially located in /home/X/Angstrom on i686
and moved to /home/Y/Angstrom on x86_64, and I manually
changed the environment file and conf files using
sed -i 's/X/Y/'
Maybe I screwed something up.
I am going to run ./oebb config beaglebone and rerun the build.
/Ulf
--
Best Regards
Ulf Samuelsson
u...@emagii.com mailto:u...@emagii.com
+46 722 427437
--
Best Regards
Ulf Samuelsson
u...@emagii.com
+46 722 427437
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] xfconf-4.10.0.bb fails on Ubuntu 12.04 LTS (x64) , maybe due to not depending on perl...
2013-12-07 01:29, Khem Raj skrev:
On Fri, Dec 6, 2013 at 2:53 PM, Ulf Samuelsson openembed...@emagii.com wrote:
recipes-xfce/xfconf/xfconf_4.10.0.bbappend:
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
EXTRA_OECONF = --disable-perl-bindings
This also results in xfconf-perl/Makefile.perl not beeing run,
and then the build completes.
I am going to try to make xfconf depend on perl instead.
Then hopefully, configure should find the perl for ARM
instead of the native perl.
You have to make sure that xfconf has proper cross tests when poking
for system capability like that. which is the real problem
here since its probablt trying to execute checks, if you point it to
target perl that will only be helpful if the execution bits somehow
can figure out the target perl capability.
The fix above to disable perl bindings is a good one since it provided
consistency even though at the expense of disabling a feature.
The problem seems to be that the PATH provided to autotools
is for the native build, and not for the target build.
But maybe this is OK.
xfconf does not understand --with-libtool-sysroot.
What is needed to change in xfconf/configure.ac to make it understand this?
--
Best Regards
Ulf Samuelsson
u...@emagii.com
+46 722 427437
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] USB hotplugging on Beaglebone Black non-functional in master branch
On 2013-10-18 10:36, Koen Kooi wrote: Op 18 okt. 2013, om 09:27 heeft Ulf Samuelsson angstrom-...@emagii.com het volgende geschreven: I have built the cloud9-gnome-image configured for beaglebone using the master branch of Angstrom and loaded it on a Beaglebone Black. The Beaglebone Black has a 5V/2A power supply. The USB hotplugging seems to not work. Know bug, pester TI to fix it. Started a crowd-funding project for this. http://igg.me/at/eMagii/x/5581172 Now it seems to work to hotplug a mouse, a keyboard and a USB serial adapter. BR Ulf If I boot without a USB-serial converter and plug it in afterwards, I do not get a new tty. If I boot with the USB-serial converter inserted, I get /dev/ttyUSB0. If I then remove the USB-serial converter /dev/ttyUSB0 remains. Using the default defconfig in meta-beagleboard which seems to enable everything USB related. Anyone seen this? Is it correct to use the beaglebone, or is beagleboard better? Which is the most stable branch for the Beaglebone Black? Whatever the setup-scripts use as default is the most stable and feature rich config. The machine for beaglebone white and black is 'beaglebone'. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Improving Build Speed
Finally got my new build machine running. so I thought I'd measure
the performance vs the old machine
Home Built
Core i7-980X
6 core/12 threads @ 3,33GHz
12 GB RAM @ 1333 Mhz.
WD Black 1 TB @ 7200 rpm
Precision 7500
2 x (X5670 6 core 2,93 MHz)
2 x (24 GB RAM @ 1333 MHz)
2 x SAS 600 GB / 15K rpm, Striped RAID
Run Angstrom Distribution
oebb.sh config beaglebone
bitbake cloud9-my-gnome-image (It is slightly extended)
The first machine build this in about three hours using
PARALLEL_MAKE = -j6
BB_NUMBER_THREADS = 6
The second machine build this much faster:
Initially tried
PARALLEL_MAKE = -j2
BB_NUMBER_THREADS = 12
but the CPU frequency tool showed it to idle.
Changed to:
PARALLEL_MAKE = -j6
BB_NUMBER_THREADS = 24
and was quicker, but it seemed to be a little flawed.
At several times during the build, the CPU frequtil
showed that most of the cores went down to
minimum frequency (2,93 GHz - 1,6 GHz)
The image build breaks down into 7658 tasks
19:36Start of Pseudo Build
19:40Start of real build
19:42Task 1000 built 2 minutes
19:45Task 2000 built 3 minutes
19:47Task 3000 built 2 minutes
19:48Task 3500 built 1 minute
19:57Task 4000 built 9 minutes ** (1)
20:00Task 4500 built 3 minutes
20:04Task 5000 built 4 minutes
20:14Task 5700 built 10 minutes
20:17Task 6000 built 3 minutes
20:27Task 6500 built 10 minutes
20:43Task 7500 built 16 minutes
20:52Task 7657 built 9 minutes *** (2)
20:59Task 7658 built 7 minutes *** (3) (do_rootfs)
Total Time 83 minutes
'***' areas with speed problems. Very little parallelism.
These times are actually after a few fixes, and the vanilla build will
be slower.
There are a few prob
There are several reasons for the speed traps.
(1) This occurs at the end of the build of the native tools
The build of the cross packages has started and stuff are unpacked
and patched, and waiting for eglibc to be ready.
(2) This occurs at the end of the build, when very few packages
are left to build so the RunQueue only contains a few packages.
Had a look at the packages built at the end.
webkit-gtk, gimp, abiword pulseaudio.
abiword has PARALLEL_MAKE = and takes forever.
I tried building an image with PARALLEL_MAKE = -j24 and this
build completes without problem.
but I have not loaded it to a target yet.
AbiWord seems to be compiling almost alone for a long time.
Webkit-gtk has a strange fix in do_compile.
do_compile() {
if [ x$MAKE = x ]; then MAKE=make; fi
...
for error_count in 1 2 3; do
...
${MAKE} ${EXTRA_OEMAKE} $@ || exit_code=1
...
done
...
}
Not sure, but I think this means that PARALLEL_MAKE might get ignored.
===
Since there are pacakges which, due to dependencies are almost
processed
alone, there is no reason to limit the parallelism for those.
Why restrict PARALLEL_MAKE to anything less than the number of H/W
threads in the machine?
Came up with a construct PARALLEL_HIGH which is defined alongside
PARALLEL_MAKE in conf/local.conf
PARALLEL_MAKE = -j8
PARALLEL_HIGH = -j24
In the appropriate recipes, which seems to be processed by bitbake
in solitude I do:
PARALLEL_HIGH ?= ${PARALLEL_MAKE}
PARALLEL_MAKE = ${PARALLEL_HIGH}
This means that they will try to use each H/W thread.
Added this to eglibc, abiword, nodejs, webkit-gtk
I thinks this could shave of maybe 5% of the build time.
===
When I looked at the bitbake runqueue stuff, it seems to prioritize
things with a lot of dependencies, which results in things like the
webkit-gtk
beeing built among the last packages.
It would probably be better if the webkit-gtk build started earlier,
so that the gimp build which depends on webkit-gtk, does not have
to run as a single task for a few minutes.
I am thinking of adding a few dummy packages which depend on
webkit-gtk and the
other long builds at the end, to fool bitbake to start their build
earlier,
but it might be a better idea, if a build hint could be part of the
recipe.
I guess a value, which could be added to the dependency count would
not be
to hard to implement (for those that know how)
(3) Creating the rootfs seems to have zero parallelism.
But I have not investigated if anything can be done.
===
So I propose the following changes:
1.Remove PARALLEL_MAKE = from abiword
2.Add the PARALLEL_HIGH variable to a few recipes.
3.Investigate if we can force the build of a few packages to an earlier
point.
===
BTW: Have noticed that there are some dependencies missing from the recipes.
DEPENDENCY BUGS
Re: [Angstrom-devel] Reg error while building Angstrom distribution for Beagleboard
2013-11-05 07:58, ganesh kumar skrev:
Dear Sir,
I am trying to build Angstrom distribution for my Beagleboard.
I followed the steps mentioned in
http://www.angstrom-distribution.org/building-angstrom;
But when I tried to build I got the below error messages,
I have seen similar problems, which disappeared when I
put the build in a directory with not so many characters in the path.
I had it in
/home/ulf/projects/Angstrom-Distribution
When I moved it to:
/home/ulf/Angstrom
the build was OK.
/Ulf
NOTE: Error during finalise of
/home/ganesh/beaglebone/setup-scripts/sources/meta-openembedded/meta-efl/recipes-core/meta/
meta-toolchain-efl.bb
ERROR: ExpansionError during parsing
/home/ganesh/beaglebone/setup-scripts/sources/meta-openembedded/meta-efl/recipes-core/meta/
meta-toolchain-efl.bb: Failure expanding variable
toolchain_create_sdk_version: ExpansionError: Failure expanding variable
METADATA_REVISION, expression was ${@base_detect_revision(d)} which
triggered exception OSError: [Errno 12] Cannot allocate memory
ERROR: Command execution failed: Exited with 1
Please point me the way to successfully build Angstrom Distribution for my
BeagleBoard.
If you need any further details of the log please let me know I will reply
immediately.
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Mix of systemd version in Angstrom Master
On 2013-11-04 01:01, Ulf Samuelsson wrote: Have built the Angstrom master for a Beaglebone. Trying to create a simple systemd service (non-forking). This fails to start. When I look into the systemd log (log_level=debug), there are references to /org/freedesktop/systemd1 which does not exist. Over the Rainbow http://www.bbc.co.uk/programmes/b03bvnf9 Instead /run/systemd exist, which I believe is present in newer systemd's. The service uses the boost, curl, curlpp and thread libraries. Uses UDP and serial port for communication. I do not use D-Bus directly, but it seems to be related to D-Bus anyway. Anyone got a clue on how to proceed? Had another look, and I was barking up the wrong tree. /usr/share/dbus-1/services contains org.freedesktop.systemd1.service My app dies when I do getenv(HOME); When I define User=root Group=root the nodeserver.service it starts without problem. Sorry to bother. BR Ulf BR Ulf Samuelsson root@beaglebone:/lib/systemd/system# dmesg [ 565.616506] systemd[1]: Accepted connection on private bus. [ 565.625796] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.StartUnit() on /org/freedesktop/systemd1 [ 565.627071] systemd[1]: Trying to enqueue job nodeserver-dbg.service/start/replace [ 565.627719] systemd[1]: Installed new job nodeserver-dbg.service/start as 1239 [ 565.627784] systemd[1]: Enqueued job nodeserver-dbg.service/start as 1239 [ 565.628048] systemd[1]: Starting ICU Nodeserver... [ 565.628539] systemd[1]: About to execute /usr/bin/nodeserver [ 565.632042] systemd[1]: Forked /usr/bin/nodeserver as 700 [ 565.637804] systemd[1]: nodeserver-dbg.service changed dead - running [ 565.637895] systemd[1]: Job nodeserver-dbg.service/start finished, result=done [ 565.637991] systemd[1]: Started ICU Nodeserver. [ 565.643147] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.GetUnit() on /org/freedesktop/systemd1 [ 565.645611] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.Get() on /org/freedesktop/systemd1/unit/nodeserver_2ddbg_2ese [ 565.646393] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local [ 565.695586] systemd[1]: Received SIGCHLD from PID 700 (nodeserver). [ 565.695940] systemd[1]: Got SIGCHLD for process 700 (nodeserver) [ 565.696349] systemd[1]: Child 700 died (code=killed, status=11/SEGV) [ 565.696377] systemd[1]: Child 700 belongs to nodeserver-dbg.service [ 565.696436] systemd[1]: nodeserver-dbg.service: main process exited, code=killed, status=11/SEGV [ 565.697576] systemd[1]: nodeserver-dbg.service changed running - failed [ 565.698397] systemd[1]: Unit nodeserver-dbg.service entered failed state [ 565.708643] systemd[1]: Accepted connection on private bus. [ 565.712325] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent [ 565.712736] systemd[1]: nodeserver-dbg.service: cgroup is empty [ 565.713126] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local [ 573.192670] systemd[1]: Accepted connection on private bus. [ 573.197976] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.GetAll() on /org/freedesktop/systemd1/unit/nodeserver_2ddbg_e [ 573.199318] systemd[1]: Looking for unit files in: [ 573.199345] systemd[1]: /etc/systemd/system [ 573.199360] systemd[1]: /lib/systemd/system [ 573.199898] systemd[1]: Looking for SysV init scripts in: [ 573.199919] systemd[1]: /etc/init.d [ 573.199939] systemd[1]: Looking for SysV rcN.d links in: [ 573.199954] systemd[1]: /etc [ 573.213709] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local [ 600.000471] systemd[1]: Timer elapsed on cpu-ondemand.timer [ 600.000520] systemd[1]: Trying to enqueue job cpu-ondemand.service/start/replace [ 600.001038] systemd[1]: Installed new job cpu-ondemand.service/start as 1287 [ 600.001121] systemd[1]: Enqueued job cpu-ondemand.service/start as 1287 [ 600.001200] systemd[1]: cpu-ondemand.timer changed waiting - running [ 600.001335] systemd[1]: Starting Switch to ondemand CPU-freq governor... [ 600.001729] systemd[1]: About to execute /usr/bin/cpufreq-set -g ondemand [ 600.003352] systemd[1]: Forked /usr/bin/cpufreq-set as 704 [ 600.006998] systemd[1]: cpu-ondemand.service changed dead - start [ 600.007118] systemd[1]: Running GC... [ 600.026202] systemd[1]: Received SIGCHLD from PID 704 (cpufreq-set). [ 600.026412] systemd[1]: Got SIGCHLD for process 704 (cpufreq-set) [ 600.026794] systemd[1]: Child 704 died (code=exited, status=0/SUCCESS) [ 600.026848] systemd[1]: Child 704 belongs to cpu-ondemand.service [ 600.026907] systemd[1]: cpu-ondemand.service: main process exited, code=exited, status=0/SUCCESS [ 600.028323] systemd[1]: cpu-ondemand.service changed start - dead [ 600.028373] systemd[1
[Angstrom-devel] Mix of systemd version in Angstrom Master
Have built the Angstrom master for a Beaglebone. Trying to create a simple systemd service (non-forking). This fails to start. When I look into the systemd log (log_level=debug), there are references to /org/freedesktop/systemd1 which does not exist. Instead /run/systemd exist, which I believe is present in newer systemd's. The service uses the boost, curl, curlpp and thread libraries. Uses UDP and serial port for communication. I do not use D-Bus directly, but it seems to be related to D-Bus anyway. Anyone got a clue on how to proceed? BR Ulf Samuelsson root@beaglebone:/lib/systemd/system# dmesg [ 565.616506] systemd[1]: Accepted connection on private bus. [ 565.625796] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.StartUnit() on /org/freedesktop/systemd1 [ 565.627071] systemd[1]: Trying to enqueue job nodeserver-dbg.service/start/replace [ 565.627719] systemd[1]: Installed new job nodeserver-dbg.service/start as 1239 [ 565.627784] systemd[1]: Enqueued job nodeserver-dbg.service/start as 1239 [ 565.628048] systemd[1]: Starting ICU Nodeserver... [ 565.628539] systemd[1]: About to execute /usr/bin/nodeserver [ 565.632042] systemd[1]: Forked /usr/bin/nodeserver as 700 [ 565.637804] systemd[1]: nodeserver-dbg.service changed dead - running [ 565.637895] systemd[1]: Job nodeserver-dbg.service/start finished, result=done [ 565.637991] systemd[1]: Started ICU Nodeserver. [ 565.643147] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.GetUnit() on /org/freedesktop/systemd1 [ 565.645611] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.Get() on /org/freedesktop/systemd1/unit/nodeserver_2ddbg_2ese [ 565.646393] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local [ 565.695586] systemd[1]: Received SIGCHLD from PID 700 (nodeserver). [ 565.695940] systemd[1]: Got SIGCHLD for process 700 (nodeserver) [ 565.696349] systemd[1]: Child 700 died (code=killed, status=11/SEGV) [ 565.696377] systemd[1]: Child 700 belongs to nodeserver-dbg.service [ 565.696436] systemd[1]: nodeserver-dbg.service: main process exited, code=killed, status=11/SEGV [ 565.697576] systemd[1]: nodeserver-dbg.service changed running - failed [ 565.698397] systemd[1]: Unit nodeserver-dbg.service entered failed state [ 565.708643] systemd[1]: Accepted connection on private bus. [ 565.712325] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent [ 565.712736] systemd[1]: nodeserver-dbg.service: cgroup is empty [ 565.713126] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local [ 573.192670] systemd[1]: Accepted connection on private bus. [ 573.197976] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Properties.GetAll() on /org/freedesktop/systemd1/unit/nodeserver_2ddbg_e [ 573.199318] systemd[1]: Looking for unit files in: [ 573.199345] systemd[1]: /etc/systemd/system [ 573.199360] systemd[1]: /lib/systemd/system [ 573.199898] systemd[1]: Looking for SysV init scripts in: [ 573.199919] systemd[1]: /etc/init.d [ 573.199939] systemd[1]: Looking for SysV rcN.d links in: [ 573.199954] systemd[1]: /etc [ 573.213709] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local [ 600.000471] systemd[1]: Timer elapsed on cpu-ondemand.timer [ 600.000520] systemd[1]: Trying to enqueue job cpu-ondemand.service/start/replace [ 600.001038] systemd[1]: Installed new job cpu-ondemand.service/start as 1287 [ 600.001121] systemd[1]: Enqueued job cpu-ondemand.service/start as 1287 [ 600.001200] systemd[1]: cpu-ondemand.timer changed waiting - running [ 600.001335] systemd[1]: Starting Switch to ondemand CPU-freq governor... [ 600.001729] systemd[1]: About to execute /usr/bin/cpufreq-set -g ondemand [ 600.003352] systemd[1]: Forked /usr/bin/cpufreq-set as 704 [ 600.006998] systemd[1]: cpu-ondemand.service changed dead - start [ 600.007118] systemd[1]: Running GC... [ 600.026202] systemd[1]: Received SIGCHLD from PID 704 (cpufreq-set). [ 600.026412] systemd[1]: Got SIGCHLD for process 704 (cpufreq-set) [ 600.026794] systemd[1]: Child 704 died (code=exited, status=0/SUCCESS) [ 600.026848] systemd[1]: Child 704 belongs to cpu-ondemand.service [ 600.026907] systemd[1]: cpu-ondemand.service: main process exited, code=exited, status=0/SUCCESS [ 600.028323] systemd[1]: cpu-ondemand.service changed start - dead [ 600.028373] systemd[1]: cpu-ondemand.timer got notified about unit deactivation. [ 600.028413] systemd[1]: cpu-ondemand.timer: Timer is elapsed. [ 600.028434] systemd[1]: cpu-ondemand.timer changed running - elapsed [ 600.029147] systemd[1]: Job cpu-ondemand.service/start finished, result=done [ 600.029246] systemd[1]: Started Switch to ondemand CPU-freq governor. [ 600.040413] systemd[1]: Accepted connection
Re: [Angstrom-devel] meta-toolchain cannot do static linking?
31 okt 2013 kl. 02:51 skrev Grissiom chaos.pro...@gmail.com: On Wed, Oct 30, 2013 at 7:29 PM, Brian Hutchinson b.hutch...@gmail.comwrote: Instead of meta-toolchain, bitbake your image with -c populate_sdk which should put the static stuff in your image and in the sysroot that is packaged with the toolchain. Don't know that this will solve your issue but it is easy to try. Thank you very much, it works like a charm! I've also add: SDKIMAGE_FEATURES += staticdev-pkgs in local.conf but it seems that this line does not help. I tried out populate_sdk yesterday, and i did not work as I would expect. It is a customized version of cloud9-gnome-image adding among other things a library libxxx. I expected that running populate_sdk on an image would generate an SDK that included *-dev for all packages in that image. That did not work. No headers for libxxx. Then I created an image with require original-image IMAGE_FEATURES += dev-pkgs which still did not give me the libxxx headers. Finally I added IMAGE_INSTALL += libxxx libxxx-dev to my original image and then I got the headers for libxxx inside the SDK. Seems like adding *-pkgs has no effect. Also, A package that gets included in the normal image due to a dependency seems to be left out, when an SDK is generated. Not 100 % sure, since I did not study this in detail. The cloud9-gnome-image seems to add a lot of headers. Have briefly scanned through its building blocks, but did not find what is adding the dev packages. Would appreciate a hint on how to remove. -—---— BTW: generating and SDK for the beaglebone for that image fails unless I add SDKIMAGE_FEATURES += asio read-edid to my local.conf, so there are some problems with those recipes. Best Regards Ulf Samuelsson -- Cheers, Grissiom ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] what file kernel configuration really uses?
28 okt 2013 kl. 09:06 skrev matti kaasinen matti.kaasi...@gmail.com:
2013/10/27 Koen Kooi k...@dominion.thruhere.net
On Wed, 2013-10-23 at 14:44 +0300, matti kaasinen wrote:
2013/10/23 Khem Raj raj.k...@gmail.com
Hi Ulf,
Yes, linux.inc seems doing the job as you told - this clears a lot.
I had
been patching wrong file:${S}/defconfig instead of
${WORKDIR}/defconfig.
It seems that I'm not alone with this mistake. ${S}/defconfig seems
to be
created by two patches:
0002-add-defconfig-file-to-use-as-.config.patch makes skeleton and
0073-defconfig-Update-bone-default-config.patch makes some
modefications.
What I mean above is that beaglebone folks have made those patches for
some
reason that is not quite clear tome now considering how ${S}/defconfig
is
produced in linux.inc.
${S}/defconfig is neither used nor produced by OE.
I was wrong in that there are two patches that create ${S}/defconfig.
Instead there are three of them:
0002-add-defconfig-file-to-use-as-.config.patch
0044-am33xx-Add-default-config.patch
0073-defconfig-Update-bone-default-config.patch
Quoted from oe_manual The patch will be applied from the unpacked source
directory, ${S}.
Above patches create and modify defconfig file. 0002-add created it and
next two tweak it slightly. I double checked this by first deleting:
${WORKDIR}/defconfig and ${S}/defconfig and then running:
bitbake -f -c unpack linux-mainline
At this point there is ${WORKDIR}/defconfig that my layer provides.
Then I run:
bitbake -f -c patch linux-mainline
Now there is also ${S}/defconfig.
Then I executed patches with those three patch files in quite a different
place - and that produced there defconfig file that was identical with
${S}/defconfig. BTW Koen, please check who has signed off:
https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/recipes-kernel/linux/linux-mainline-3.8/not-capebus/0002-add-defconfig-file-to-use-as-.config.patch
He might be someone you know :-)
So, I would say OE produces ${S}/defconfig.
But in the end, it is ignored...
It is probably a leftover...
/ulf
${WORKDIR}/defconfig (important one) is most likely coming from
./linux/linux-mainline-3.8/beaglebone/defconfig as there is only
one
difference that could have come from configuration process.
It seems that configuration fragments do not work in regular
Angstrom - I
suppose they are just Yocto stuff.
yes.
Providing defconfig directly did not work - most likely it was
written
over
by the patching the seems creating the ${WORKDIR}/defconfig
what do you mean ? defconfig is provided as any other file and then
munged
over
in WORKDIR to make a .config
This is outdated information - wild quess - before I noticed how that
${S}/defconfig was really generated by those patches I explained above.
As I said above, ${S}/defconfig is not used in the build.
Good to know
Thanks
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] what file kernel configuration really uses?
I have noticed this as well and it is highly irritating,
Best Regards
Ulf Samuelsson
28 okt 2013 kl. 09:23 skrev matti kaasinen matti.kaasi...@gmail.com:
There is another question, I think I mentioned it earlier also in this
chain. I have also asked it in other time as own subject. No-one seems to
have opinion about that.
Koen, you might know, if it is a feature misbehaviour or problem in my
set-up.
For instance when I ran those tests I did first fetch. Then I ran
unpack. Unpacking ran again fetch and then unpack. Then I ran patch.
Again, at least unpack was run again and then patch. Similar behaviour
seems to happen with configure so that patch will be run again even
though it had been ran manually before. This feature makes paching quite
awkward as if I edit some file that has been unpacked and applied with
other patches, that will be written over when running configure or
compile to check how edits worked.
I always get two warnings when I run bitbake:
WARNING: No recipes available for:
/home/sw/cpr3/oe/sources/meta-handheld/recipes-core/udev/udev_164.bbappend
/home/sw/cpr3/oe/sources/meta-intel/meta-fri2/recipes-core/tiny-init/tiny-init.bbappend
But I suppose they are nothing to do with this issue.
So, Is this something that should happen or should I try to find set-up
problem of some kind?
Thanks,
Matti
2013/10/28 matti kaasinen matti.kaasi...@gmail.com
2013/10/27 Koen Kooi k...@dominion.thruhere.net
On Wed, 2013-10-23 at 14:44 +0300, matti kaasinen wrote:
2013/10/23 Khem Raj raj.k...@gmail.com
Hi Ulf,
Yes, linux.inc seems doing the job as you told - this clears a lot.
I had
been patching wrong file:${S}/defconfig instead of
${WORKDIR}/defconfig.
It seems that I'm not alone with this mistake. ${S}/defconfig seems
to be
created by two patches:
0002-add-defconfig-file-to-use-as-.config.patch makes skeleton and
0073-defconfig-Update-bone-default-config.patch makes some
modefications.
What I mean above is that beaglebone folks have made those patches for
some
reason that is not quite clear tome now considering how ${S}/defconfig
is
produced in linux.inc.
${S}/defconfig is neither used nor produced by OE.
I was wrong in that there are two patches that create ${S}/defconfig.
Instead there are three of them:
0002-add-defconfig-file-to-use-as-.config.patch
0044-am33xx-Add-default-config.patch
0073-defconfig-Update-bone-default-config.patch
Quoted from oe_manual The patch will be applied from the unpacked source
directory, ${S}.
Above patches create and modify defconfig file. 0002-add created it and
next two tweak it slightly. I double checked this by first deleting:
${WORKDIR}/defconfig and ${S}/defconfig and then running:
bitbake -f -c unpack linux-mainline
At this point there is ${WORKDIR}/defconfig that my layer provides.
Then I run:
bitbake -f -c patch linux-mainline
Now there is also ${S}/defconfig.
Then I executed patches with those three patch files in quite a different
place - and that produced there defconfig file that was identical with
${S}/defconfig. BTW Koen, please check who has signed off:
https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/recipes-kernel/linux/linux-mainline-3.8/not-capebus/0002-add-defconfig-file-to-use-as-.config.patch
He might be someone you know :-)
So, I would say OE produces ${S}/defconfig.
${WORKDIR}/defconfig (important one) is most likely coming from
./linux/linux-mainline-3.8/beaglebone/defconfig as there is
only one
difference that could have come from configuration process.
It seems that configuration fragments do not work in regular
Angstrom - I
suppose they are just Yocto stuff.
yes.
Providing defconfig directly did not work - most likely it was
written
over
by the patching the seems creating the ${WORKDIR}/defconfig
what do you mean ? defconfig is provided as any other file and then
munged
over
in WORKDIR to make a .config
This is outdated information - wild quess - before I noticed how that
${S}/defconfig was really generated by those patches I explained above.
As I said above, ${S}/defconfig is not used in the build.
Good to know
Thanks
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] what file kernel configuration really uses?
You are looking in the wrong file.
In Angstrom, you need to change BBPATH in setup-scripts/conf/bblayers.conf
Not in the layer.conf in your own layer.
Best Regards
Ulf Samuelsson
u...@emagii.com
23 okt 2013 kl. 14:24 skrev matti kaasinen matti.kaasi...@gmail.com:
2013/10/23 matti kaasinen matti.kaasi...@gmail.com
for conf and include files it will use the BBPATH and not priority
which means your layer should appear before meta-beagleboard in BBPATH
order.
It did not help chnging BBPATH in layer.conf
It used to be
BBPATH .= :${LAYERDIR}
and I changed it to:
BBPATH =. ${LAYERDIR}:
It still fetches beaglebone's defconfig.
Should I change my bbappend file instad not using FILESEXTRAPATHS_prepend
but using FILESPATH_prepend instead?
Do FILESPATH have precedence over FILESEXTRAPATHS?
Cheers,
Matti
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] v2013.06 and v2013.12 architecture change for ARMv7A machines
Best Regards
Ulf Samuelsson
u...@emagii.com
+46 (722) 427 437
23 okt 2013 kl. 18:30 skrev Björn Krombholz pir...@gmail.com:
On 10/20/2013 09:04 PM, Koen Kooi wrote:
Then I noticed that the 'genericarmv7a' machine in meta-linaro set
the DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set
that variable, but that's a different bug. It turns out that using
that tune we can have a single feed again for all armv7a machines.
Hi,
just for clarification, I'm not sure where to set it if not in the MACHINE
config without modifying meta-angstrom.
I've seen you added MACHINE specific DEFAULTTUNEs based on the currently
supported boards.
Basically the result should be (IMHO):
if MACHINE is a armv7a based and DISTRO is angstrom, then
DEFAULTTUNE = armv7athf-neon
Since not all arm7va have neon. it is optional on Cortex-A5
and there are already arm7a chips without neon round,
so this is not a good idea.
Would it be possible to add those definitions based on SOC_FAMILY:
DEFAULTTUNE_ti33x and DEFAULTTUNE_omap3?
Better.
As of now, when I add a new MACHINE=machfoo based on ti33x.inc from meta-ti,
I end up with a DEFAULTTUNE=armv7a-neon instead of the new one, as the board
is not known in meta-angstrom.
I added
DEFAULTTUNE_machfoo = ${DEFAULTTUNE_genericarmv7a}
to the machfoo.conf which is discouraged, if I understand you correctly.
Maybe I'm just missing the obvious safe way?
Thx
Björn
--
Björn Krombholz
pironex GmbH -- http://www.pironex.de
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] what file kernel configuration really uses?
The defconfig file is present in the meta-layers and copied to the kernel build directory. It is used to create the .config file in the kernel source directory. If you modify the .config file, you will see changes in the kernel file. if you modify the defconfig file in the build directory, nothing happens. I typically change the .config and copy the result to the defconfig in the meta-layer. Then I rebuild from scratch. bitbake -c cleansstate virtual/kernel bitbake virtual/kernel Best Regards Ulf Samuelsson u...@emagii.com +46 (722) 427 437 22 okt 2013 kl. 14:04 skrev matti kaasinen matti.kaasi...@gmail.com: Hi! What configuration kernel build really uses - .config or defconfig? It seems, that menuconfig (bitbake -c menuconfig ) use always .config file. I have problem that changes in defconfig are not seen in kernel features. Instead they seem the same that are in .config file I have tried configuration fragments, patches and providing defconfig directly. They all seem to give proper defconfig. However, menuconfig never provide the changed configurations. Also, for instance when I try to configure HW EEC operation for NAND flash using CONFIG_MTD_NAND_OMAP_BCH. omap2.c reports that CONFIG_MTD_NAND_OMAP_BCH is not enabled. I've been workin on beaglebone variant - layer over beaglebone. Build Configuration: BB_VERSION= 1.17.0 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beaglebone DISTRO= angstrom DISTRO_VERSION= v2012.12 TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon oe_sitecno oe_emergence = unknown:unknown meta-angstrom = angstrom-v2012.12-yocto1.3:b7f8207b94d9a0ece73ad212a193cb2c95bd17ee These setting give kernel 3.8.11. Is there something I have missed? Thanks in advance, Matti ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] what file kernel configuration really uses?
On 2013-10-22 17:20, matti kaasinen wrote:
Thanks Ulf,
It seems to work in that way. However, I'm a bit surprised that it works so
as as I mentioned above all the procedures -
patching defconfig in the kernel build directory, providing defconfig in
metadata and providing configuration fragments as described in the Yocto
Kernel development manual - give the same outcome in the defconfig at the
kernel build directory.
What is happening is dependent on the kernel recipe.
Typically, you find that linux.inc does the job,
and in do_configure, which is run when you do:
bitbake -c configure virtual/kernel
${WORKDIR}/defconfig is altered to ensure it makes sense.
A lot of options are simply deleted.
${S}/.config is created as an empty file and then the deleted options
are added with a proper value.
At the end, defconfig is appended to the ${S}/.config
so when you run
bitbake -c configure virtual/kernel
both ${WORKDIR}/defconfig and ${S}/.config are changed.
/Ulf
What command do you use when you are using .config directly? My experience
is that when I for instance run:
bitbake -f -c configure virtual/kernel
after
bitbake -f -c patch virtual/kernel
bitbake executes again do_patch, that at least rides over defconfig if I
edited that.
In fact it seems that bitbake -c config runs always do_patch even if
previous command was patch and no modifications were in between.
BR,
Matti
2013/10/22 Ulf Samuelsson angstrom-...@emagii.com
The defconfig file is present in the meta-layers and copied to the
kernel build directory.
It is used to create the .config file in the kernel source directory.
If you modify the .config file, you will see changes in the kernel file.
if you modify the defconfig file in the build directory, nothing happens.
I typically change the .config and copy the result to the defconfig in
the
meta-layer. Then I rebuild from scratch.
bitbake -c cleansstate virtual/kernel
bitbake virtual/kernel
Best Regards
Ulf Samuelsson
u...@emagii.com
+46 (722) 427 437
22 okt 2013 kl. 14:04 skrev matti kaasinen matti.kaasi...@gmail.com:
Hi!
What configuration kernel build really uses - .config or defconfig?
It seems, that menuconfig (bitbake -c menuconfig ) use always .config
file.
I have problem that changes in defconfig are not seen in kernel features.
Instead they seem the same that are in .config file
I have tried configuration fragments, patches and providing defconfig
directly.
They all seem to give proper defconfig. However, menuconfig never provide
the changed configurations. Also, for instance when I try to configure HW
EEC operation for NAND flash using CONFIG_MTD_NAND_OMAP_BCH.
omap2.c reports that CONFIG_MTD_NAND_OMAP_BCH is not enabled.
I've been workin on beaglebone variant - layer over beaglebone.
Build Configuration:
BB_VERSION= 1.17.0
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = beaglebone
DISTRO= angstrom
DISTRO_VERSION= v2012.12
TUNE_FEATURES = armv7a vfp neon cortexa8
TARGET_FPU= vfp-neon
oe_sitecno
oe_emergence = unknown:unknown
meta-angstrom =
angstrom-v2012.12-yocto1.3:b7f8207b94d9a0ece73ad212a193cb2c95bd17ee
These setting give kernel 3.8.11.
Is there something I have missed?
Thanks in advance,
Matti
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] USB hotplugging on Beaglebone Black non-functional in master branch
On 2013-10-18 10:36, Koen Kooi wrote:
Op 18 okt. 2013, om 09:27 heeft Ulf Samuelsson angstrom-...@emagii.com het
volgende geschreven:
I have built the cloud9-gnome-image configured for beaglebone
using the master branch of Angstrom and loaded it on a Beaglebone Black.
The Beaglebone Black has a 5V/2A power supply.
The USB hotplugging seems to not work.
Know bug, pester TI to fix it.
When I remove something from the beaglebone USB host connector I get:
musb_stage0_irq 790: unhandled DISCONNECT transition (a_idle)
What I can see from the code, is that there is only one way to enter
OTG_STATE_A_IDLE-
- if you get an interrupt and the MUSB_INTR_SESSREQ flag is set
Then this mode is set:
musb-xceiv-state = OTG_STATE_A_IDLE;
AFAIK, I.E, it is now an idle OTG peripheral (not a host)
Havent looked through everything yet, but I am yet to find a place where
you exit this state.
If the driver is in this state, then basically every event gets ignored.
In musb_core.c there is no place where
switch(musb-xceiv-state)
has a
case OTG_STATE_A_IDLE: ...
There is a CONFIG_USB_GADGET_MUSB_HDRC which is clear,
If this means that the HDRC can work in OTG mode switching between host
and device,
and the CONFIG item is unchecked, then you should never be in a
peripheral state, right?
The symptom occur when the driver handles a disconnect interrupt.
It falls through to the default, and you get the error
if ((int_usb MUSB_INTR_DISCONNECT) !musb-ignore_disconnect) {
DEV_DBG(musb-controller, DISCONNECT (%s) as %s, devctl %02x\n,
otg_state_string(musb-xceiv-state),
MUSB_MODE(musb), devctl);
handled = IRQ_HANDLED;
switch (musb-xceiv-state) {
case OTG_STATE_A_HOST:
case OTG_STATE_A_SUSPEND:
usb_hcd_resume_root_hub(musb_to_hcd(musb));
musb_root_disconnect(musb);
if (musb-a_wait_bcon != 0)
musb_platform_try_idle(musb, jiffies
+ msecs_to_jiffies(musb-a_wait_bcon));
break;
case OTG_STATE_B_HOST:
/* REVISIT this behaves for real disconnect
* cases; make sure the other transitions from
* from B_HOST act right too. The B_HOST code
* in hnp_stop() is currently not used...
*/
musb_root_disconnect(musb);
musb_to_hcd(musb)-self.is_b_host = 0;
musb-xceiv-state = OTG_STATE_B_PERIPHERAL;
MUSB_DEV_MODE(musb);
musb_g_disconnect(musb);
break;
case OTG_STATE_A_PERIPHERAL:
musb_hnp_stop(musb);
musb_root_disconnect(musb);
/* FALLTHROUGH */
case OTG_STATE_B_WAIT_ACON:
/* FALLTHROUGH */
case OTG_STATE_B_PERIPHERAL:
case OTG_STATE_B_IDLE:
musb_g_disconnect(musb);
break;
default:
WARNING((%s) unhandled DISCONNECT transition\n,
otg_state_string(musb-xceiv-state));
break;
}
}
If I boot without a USB-serial converter and plug it in afterwards, I do not
get a new tty.
If I boot with the USB-serial converter inserted, I get /dev/ttyUSB0.
If I then remove the USB-serial converter /dev/ttyUSB0 remains.
Using the default defconfig in meta-beagleboard which seems to enable
everything USB related.
Anyone seen this?
Is it correct to use the beaglebone, or is beagleboard better?
Which is the most stable branch for the Beaglebone Black?
Whatever the setup-scripts use as default is the most stable and feature rich
config. The machine for beaglebone white and black is 'beaglebone'.
regards,
Koen
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] v2013.06 and v2013.12 architecture change for ARMv7A machines
On 2013-10-21 07:52, Koen Kooi wrote:
Op 20 okt. 2013, om 23:49 heeft Ulf Samuelsson angstrom-...@emagii.com het
volgende geschreven:
20 okt 2013 kl. 21:04 skrev Koen Kooi k...@dominion.thruhere.net:
Hi,
A while ago we decided to switch armv7a machines for hardfloat because we were
worn it with explaining that there's no real world difference between softfp
(which does use hw fp despite its name) and hardfp and silicon vendors started
moving their evil binary only stuff to that as well. So we looked into it and
set the DEFAULTTUNE to cortexa8hf-neon. That gave us a hardfp build and it had
no regressions so far, so good.
So how are Cortex-A5 chips without neon going to be handled?
They are also armv7a!
I'd say DEFAULTTUNE = armv7athf and a seperate feed. We did something similar
in the 2011.03 release for the armv6-without-vfp chips.
Here is my tune-cortexa5.inc.
Can build systemd-gnome-image with this.
DEFAULTTUNE ?= cortexa5thf
# TUNE_FEATURES = armv7a vfp callconvention-hard
# TARGET_FPU= vfp
require conf/machine/include/arm/arch-armv7a.inc
TUNEVALID[cortexa5] = Enable Cortex-A5 specific processor optimizations
TUNE_CCARGS += ${@bb.utils.contains(TUNE_FEATURES, cortexa5,
-mtune=cortex-a5, , d)}
# Little Endian base configs
AVAILTUNES += cortexa5 cortexa5t
TUNE_FEATURES_tune-cortexa5 = ${TUNE_FEATURES_tune-armv7a} cortexa5
TUNE_FEATURES_tune-cortexa5t = ${TUNE_FEATURES_tune-armv7at} cortexa5
PACKAGE_EXTRA_ARCHS_tune-cortexa5 = ${PACKAGE_EXTRA_ARCHS_tune-armv7a}
PACKAGE_EXTRA_ARCHS_tune-cortexa5t = ${PACKAGE_EXTRA_ARCHS_tune-armv7at}
# VFP Tunes
AVAILTUNES += cortexa5hf cortexa5thf
TUNE_FEATURES_tune-cortexa5hf ?= ${TUNE_FEATURES_tune-armv7ahf} cortexa5
TUNE_FEATURES_tune-cortexa5thf ?= ${TUNE_FEATURES_tune-armv7athf} cortexa5
PACKAGE_EXTRA_ARCHS_tune-cortexa5hf = ${PACKAGE_EXTRA_ARCHS_tune-armv7ahf}
PACKAGE_EXTRA_ARCHS_tune-cortexa5thf =
${PACKAGE_EXTRA_ARCHS_tune-armv7athf}
Been struggling with this, during the weekend, since some recipes assume hat if
It is an arm7a, then Neon should be turned on.
Those have to be converted to check TUNE_FEATURES for 'neon'.
regards,
Koen
Best Regards
Ulf Samuelsson
u...@emagii.com
Two weeks ago I switched jobs and had to dust off my pandaboards for the new
job and that's were things starting going south. 'cortexa8hf-neon' didn't work
since the buildsystem knew it was an cortex-A9 CPU, so 'cortexa9hf-neon' needed
to be used. Again that built and worked. But it required two seperate feeds
that were a single feed in v2012.12 and earlier. Then I started looking at
cortex-A15 boards and realized this setup is wasting disk space and cpu time.
Then I noticed that the 'genericarmv7a' machine in meta-linaro set the
DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set that variable,
but that's a different bug. It turns out that using that tune we can have a
single feed again for all armv7a machines. Yay!
If you have been using v2013.06 and your architecture for the feeds is
cortexa*hf*, try doing the following:
opkg update ; opkg install angstrom-feed-configs
opkg update ; opkg install opkg-config-base
That will update the feed configs to point to the new unified feed and drag in
the /etc/opkg/arch.conf that lists the new armv7ahf-vfp-neon architecture as
supported. It will throw a ton of warnings for the currently installed
packages, but that's mostly harmless. Installing things from the feeds will
work again, but it will try to reinstall a lot of things due to the
architecture change.
The v2013.12 feed will be cleaned up later, all the conferences will interfere
with that.
It looks like the complete angstrom cabal will be present at ELC-E in Edinburgh
next week and at least 3 of us will also be attending Linaro Connect USA the
week after that. If you're in the neighbourhood come say hello and please tell
us about your pet peeve with angstrom or OE and we'll try to address it.
thanks,
Koen
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Using the correct xserver-xf86-config_0.1.bbappend
Trying to build a systemd-gnome-image raspberrypi under Angstrom, with a few extra layers. This fails on xserver-xf86-config_0.1.[bb|bbappend] The extra layer has BBPRIORITY = 20. meta-beagleboard has BBPRIORITY = 8 meta-raspberrypi has BBPRIORITY = 6 (later changed to 120) BBLAYERS are in the order meta-extra layer meta-beagleboard meta-raspberrypi It looks like bitbake will select the bbappend in the layer with the highest priority, even if that contains a COMPATIBLE_MACHINE clause, which does not include the current MACHINE. /Is there any way to make bitbake select the correct bbappend file without modifying the BBPRIORITY? / Looks like the xserver-xf86-config for the raspberry-pi fails on *SRC_URI_append_raspberrypi = file://xorg.conf.d/*** * When I change to: *SRC_URI_append_raspberrypi = file://xorg.conf.d/10-evdev.conf * the raspberry pi version completes. /Wildcards are not allowed?/ -- Best Regards Ulf Samuelsson eMagii ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [OE-core] Using the correct xserver-xf86-config_0.1.bbappend
On 2013-10-21 22:21, Khem Raj wrote: Ulf On Mon, Oct 21, 2013 at 9:30 AM, Ulf Samuelsson openembedded-c...@emagii.com wrote: Trying to build a systemd-gnome-image raspberrypi under Angstrom, with a few extra layers. This fails on xserver-xf86-config_0.1.[bb|bbappend] The extra layer has BBPRIORITY = 20. meta-beagleboard has BBPRIORITY = 8 meta-raspberrypi has BBPRIORITY = 6 (later changed to 120) BBLAYERS are in the order meta-extra layer meta-beagleboard meta-raspberrypi It looks like bitbake will select the bbappend in the layer with the highest priority, Not really. All bbappends are selected the order or sequence of them is governed by how the layers line up in BBPATH Hm, it seemed to work if I increased the BBPRIORITY. Either method seems to be problematic. If you build for a certain machine, then you want to define which bbappend to use regardless of BBPATH or BBPRIORITY. Maybe bitbake needs to know which meta-layer contains the machine.conf, and always select a bbappend in that layer, over bbappends in other layers. Otherwise you have to edit bblayer.conf every time you want to switch to a new machine, which I think is undesirable. even if that contains a COMPATIBLE_MACHINE clause, which does not include the current MACHINE. Is there any way to make bitbake select the correct bbappend file without modifying the BBPRIORITY? Looks like the xserver-xf86-config for the raspberry-pi fails on SRC_URI_append_raspberrypi = file://xorg.conf.d/* When I change to: SRC_URI_append_raspberrypi = file://xorg.conf.d/10-evdev.conf the raspberry pi version completes. Wildcards are not allowed? This is a question of fundamental bitbake semantics/syntax for SRC_URI and nothing to do with bbappends. and I dont think wildcards in SRC_URI are reliable, so better be explicit about them. Yes, since this problem occured at the same time, I thought that I'd mention it as well. Basically the any image build for raspberry pi involving X is broken then. /Ulf -- Best Regards Ulf Samuelsson eMagii ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- Best Regards Ulf Samuelsson u...@emagii.com +46 722 427437 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] v2013.06 and v2013.12 architecture change for ARMv7A machines
20 okt 2013 kl. 21:04 skrev Koen Kooi k...@dominion.thruhere.net: Hi, A while ago we decided to switch armv7a machines for hardfloat because we were worn it with explaining that there's no real world difference between softfp (which does use hw fp despite its name) and hardfp and silicon vendors started moving their evil binary only stuff to that as well. So we looked into it and set the DEFAULTTUNE to cortexa8hf-neon. That gave us a hardfp build and it had no regressions so far, so good. So how are Cortex-A5 chips without neon going to be handled? They are also armv7a! Been struggling with this, during the weekend, since some recipes assume hat if It is an arm7a, then Neon should be turned on. Best Regards Ulf Samuelsson u...@emagii.com Two weeks ago I switched jobs and had to dust off my pandaboards for the new job and that's were things starting going south. 'cortexa8hf-neon' didn't work since the buildsystem knew it was an cortex-A9 CPU, so 'cortexa9hf-neon' needed to be used. Again that built and worked. But it required two seperate feeds that were a single feed in v2012.12 and earlier. Then I started looking at cortex-A15 boards and realized this setup is wasting disk space and cpu time. Then I noticed that the 'genericarmv7a' machine in meta-linaro set the DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set that variable, but that's a different bug. It turns out that using that tune we can have a single feed again for all armv7a machines. Yay! If you have been using v2013.06 and your architecture for the feeds is cortexa*hf*, try doing the following: opkg update ; opkg install angstrom-feed-configs opkg update ; opkg install opkg-config-base That will update the feed configs to point to the new unified feed and drag in the /etc/opkg/arch.conf that lists the new armv7ahf-vfp-neon architecture as supported. It will throw a ton of warnings for the currently installed packages, but that's mostly harmless. Installing things from the feeds will work again, but it will try to reinstall a lot of things due to the architecture change. The v2013.12 feed will be cleaned up later, all the conferences will interfere with that. It looks like the complete angstrom cabal will be present at ELC-E in Edinburgh next week and at least 3 of us will also be attending Linaro Connect USA the week after that. If you're in the neighbourhood come say hello and please tell us about your pet peeve with angstrom or OE and we'll try to address it. thanks, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] USB hotplugging on Beaglebone Black non-functional in master branch
I have built the cloud9-gnome-image configured for beaglebone using the master branch of Angstrom and loaded it on a Beaglebone Black. The Beaglebone Black has a 5V/2A power supply. The USB hotplugging seems to not work. If I boot without a USB-serial converter and plug it in afterwards, I do not get a new tty. If I boot with the USB-serial converter inserted, I get /dev/ttyUSB0. If I then remove the USB-serial converter /dev/ttyUSB0 remains. Using the default defconfig in meta-beagleboard which seems to enable everything USB related. Anyone seen this? Is it correct to use the beaglebone, or is beagleboard better? Which is the most stable branch for the Beaglebone Black? Still using Ubuntu 12.04 for the build, so a.3/1.4/1.5 does not build, but my 2 x Xeon X5670 machine delivered yesterday :-) is behind my back, doing nothing, so maybe installing OpenSuSE on that is a better plan. BR Ulf Samuelsson ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] USB hotplugging on Beaglebone Black non-functional in master branch
On 2013-10-18 10:36, Koen Kooi wrote: Op 18 okt. 2013, om 09:27 heeft Ulf Samuelsson angstrom-...@emagii.com het volgende geschreven: I have built the cloud9-gnome-image configured for beaglebone using the master branch of Angstrom and loaded it on a Beaglebone Black. The Beaglebone Black has a 5V/2A power supply. The USB hotplugging seems to not work. Know bug, pester TI to fix it. Is this present since day one? Could revert to an older kernel if that helps. No USB - no project... /Ulf If I boot without a USB-serial converter and plug it in afterwards, I do not get a new tty. If I boot with the USB-serial converter inserted, I get /dev/ttyUSB0. If I then remove the USB-serial converter /dev/ttyUSB0 remains. Using the default defconfig in meta-beagleboard which seems to enable everything USB related. Anyone seen this? Is it correct to use the beaglebone, or is beagleboard better? Which is the most stable branch for the Beaglebone Black? Whatever the setup-scripts use as default is the most stable and feature rich config. The machine for beaglebone white and black is 'beaglebone'. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Issues with PREFERRED_VERSION/PREFERRED_PROVIDER for the kernel
1. If you define something in the MACHINE.conf and in DISTRO.conf then DISTRO.conf has higher priority. This is really non-intuitive. 2. If you define a PREFERRED_VERSION which does not have a corresponding .bb file you do not get a warning, and the latest PREFERRED_PROVIDER is used. 3. If you define a PREFERRED_PROVIDER which does not have a corresponding .bb file you *do* get a warning, with a list of possible providers, and bitbake will bake the first in the list. It will also bake the *latest* version, even if that provider has a PREFERRED_VERSION. 4. If I define PREFERRED_PROVIDER_virtual/kernel = linux-x in machine.conf, bitbake will bake linux-x using the latest version 5. If I define PREFERRED_VERSION_virtual/kernel = 3.7.0, this is ignored. 6. If I define PREFERRED_VERSION_linux-x = 3.7.0, this is accepted and linux-x_3.7.0.bb is used. --- Questions: You need to parse machine.conf before you parse the DISTRO since some things in the distro is machine dependent. I.E: PREFERRED_VERSION_binutils_avr32 = 2.17 (1) Would it be possible to reparse machine.conf after DISTRO has been parsed, resetting some stuff, overridden by the DISTRO? (2) Why no warning, if the PREFERRED_VERSION cannot be found. It would be good to have which versions are available. For the Beaglebone, you have a linux-mainline_3.7.bb, but if you set PREFERRED_VERSION_linux-mainline = 3.7 you still get 3.8.13 built, because linux-mainline_3.7.bb contains PV = 3.7.0 A warning would have been helpful! (3) Why is PREFERRED_VERSION_virtual/kernel accepted without error message, but ignored? (4) If bitbake cannot find a recommended PROVIDER, and selects something else, why not use the PREFERRED_VERSION if it exists? BR Ulf Samuelsson ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [OE-core] Issues with PREFERRED_VERSION/PREFERRED_PROVIDER for the kernel
In some cases, you might want to override a few things in the DISTRO. Maybe an easy way to handle this would be if the DISTRO conf file included an empty file at the end, which can be overridden by a file in your own layer. Best Regards Ulf Samuelsson 18 okt 2013 kl. 18:31 skrev Koen Kooi k...@dominion.thruhere.net: Op 18 okt. 2013, om 17:59 heeft Ulf Samuelsson angstrom-...@emagii.com het volgende geschreven: 1. If you define something in the MACHINE.conf and in DISTRO.conf then DISTRO.conf has higher priority. This is really non-intuitive. It is correct however, if the DISTRO defines it, it's a DISTRO setting that a MACHINE.conf really should stay away from. regards, KOen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [OE-core] Problems when building Angstrom master 1.3 1.4 for Beagleboard Black
On 2013-10-14 20:31, Khem Raj wrote: On Oct 11, 2013, at 8:33 AM, Ulf Samuelsson angstrom-...@emagii.com wrote: On 2013-10-11 16:58, Koen Kooi wrote: Op 11 okt. 2013, om 16:32 heeft Ulf Samuelsson angstrom-...@emagii.com het volgende geschreven: Have tried out building Angstrom for Beaglebone Black on a Quad-Core i7/Ubuntu 12.04 i386 with: I strongly recommend ditching ubuntu and installing linux instead. I don't know what causes it, but switching to debian, arch, gentoo, fedora, opensuse or anything else not ubuntu based gets rid off all problems with builds not working, not booting, etc. OK, after installing 12.04LTS I have to 1. left-click (hold) 2. alt (hold) 3. right click just to add an item to the panel, I guess they are trying to prove that Ubuntu One is superior to gnome, by making gnome successively worse. so I am quite pissed of with Ubuntu Getting a dual Xeon 6-core next week, so I'll wait until then, but that is not going to be exposed to Ubuntu ever… What is your default shell ? I would recomment to use bash. bash it is. BR Ulf BR Ulf PARALLEL_MAKE = -j8 BB_NUMBER_THREADS = 8 I bitbake cloud9-gnome-image RESULTS: * remotes/origin/angstrom-v2013.06-yocto1.4commit 246357a1cc4977683ada564d38218e837ac615e3 image builds but does not boot. * remotes/origin/angstrom-v2012.12-yocto1.3commit 01984cc460acfe5e7d5bab4feeb0888d5c6fe77f image builds but does not boot. * origin/master commit 7a3b004f7bfa24ea54b0da78bd80e4dd7839321d Build fails on two issues. 1.libxklavier compile fails. | xklavier.c: In function 'xkl_engine_class_init': | xklavier.c:846:8: error: 'XKL_TYPE_ENGINE_FEATURES' undeclared (first use in this function) ... Summary: 1 task failed: /home/ulf/projects/ICU/Angstrom/setup-scripts/sources/meta-openembedded/meta-gnome/recipes-gnome/libxklavier/libxklavier_5.0.bb, do_compile Did bitbake -c cleansstate libxklavier and restarted, and then it continued without problem, so there seem to be a dependency problem. 2.nodejs compiles fails with error: | arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/beaglebone '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DL_ENDIAN' '-DOPENSSL_THREADS' '-DPURIFY' '-D_REENTRANT' '-DOPENSSL_NO_DTLS1' '-DOPENSSL_NO_SOCK' '-DOPENSSL_NO_DGRAM' '-DOPENSSL_NO_GOST' '-DOPENSSL_NO_HW_PADLOCK' '-DOPENSSL_NO_ASM' '-DENGINESDIR=/dev/null' '-DOPENSSLDIR=/etc/ssl' '-DTERMIOS' -I../deps/openssl -I../deps/openssl/openssl -I../deps/openssl/openssl/crypto -I../deps/openssl/openssl/crypto/asn1 -I../deps/openssl/openssl/crypto/evp -I../deps/openssl/openssl/crypto/store -I../deps/openssl/openssl/include -I../deps/openssl/config/android -Wall -pthread -O2 -fno-strict-aliasing -fno-tree-vrp -MMD -MF /home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/node js-0.8.22-r0/node-v0.8.22/out/Release/.deps//home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/whrlpool/wp_block.o.d.raw -O2 -pipe -g -feliminate-unused-debug-types -c -o /home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/whrlpool/wp_block.o ../deps/openssl/openssl/crypto/whrlpool/wp_block.c | make[1]: execvp: printf: Argument list too long I get the second problem when I run from: /home/ulf/projects/ICU/Angstrom/setup-scripts/ When I install Angstrom in /home/icu/v2012.12 I do not see the problem. --- Have tried recompiling my kernel changing include/linux/binfmts.h # define MAX_ARG_PAGES32 # define MAX_ARG_PAGES64 based on something I found on Internet, to no avail. Checking a little bit more, I see it looks like: #ifdef CONFIG_MMU ... #else # define MAX_ARG_PAGES64 struct page *page[MAX_ARG_PAGES]; #endif CONFIG_MMU is set, so the change is in part of the code which is not used Maybe there should be some kind of warning about how deep in the directory structure Angstrom can be. --- The resulting kernel/filesystem will run on the Beagleboard Black. Anyone knows what to change to increase the argument area on linux-3.2.x? BR Ulf Samuelsson ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[Angstrom-devel] Problems when building Angstrom master 1.3 1.4 for Beagleboard Black
Have tried out building Angstrom for Beaglebone Black on a Quad-Core i7/Ubuntu 12.04 i386 with: PARALLEL_MAKE = -j8 BB_NUMBER_THREADS = 8 I bitbake cloud9-gnome-image RESULTS: * remotes/origin/angstrom-v2013.06-yocto1.4commit 246357a1cc4977683ada564d38218e837ac615e3 image builds but does not boot. * remotes/origin/angstrom-v2012.12-yocto1.3commit 01984cc460acfe5e7d5bab4feeb0888d5c6fe77f image builds but does not boot. * origin/master commit 7a3b004f7bfa24ea54b0da78bd80e4dd7839321d Build fails on two issues. 1.libxklavier compile fails. | xklavier.c: In function 'xkl_engine_class_init': | xklavier.c:846:8: error: 'XKL_TYPE_ENGINE_FEATURES' undeclared (first use in this function) ... Summary: 1 task failed: /home/ulf/projects/ICU/Angstrom/setup-scripts/sources/meta-openembedded/meta-gnome/recipes-gnome/libxklavier/libxklavier_5.0.bb, do_compile Did bitbake -c cleansstate libxklavier and restarted, and then it continued without problem, so there seem to be a dependency problem. 2.nodejs compiles fails with error: | arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/beaglebone '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DL_ENDIAN' '-DOPENSSL_THREADS' '-DPURIFY' '-D_REENTRANT' '-DOPENSSL_NO_DTLS1' '-DOPENSSL_NO_SOCK' '-DOPENSSL_NO_DGRAM' '-DOPENSSL_NO_GOST' '-DOPENSSL_NO_HW_PADLOCK' '-DOPENSSL_NO_ASM' '-DENGINESDIR=/dev/null' '-DOPENSSLDIR=/etc/ssl' '-DTERMIOS' -I../deps/openssl -I../deps/openssl/openssl -I../deps/openssl/openssl/crypto -I../deps/openssl/openssl/crypto/asn1 -I../deps/openssl/openssl/crypto/evp -I../deps/openssl/openssl/crypto/store -I../deps/openssl/openssl/include -I../deps/openssl/config/android -Wall -pthread -O2 -fno-strict-aliasing -fno-tree-vrp -MMD -MF /home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/.deps//home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/whrlpool/wp_block.o.d.raw -O2 -pipe -g -feliminate-unused-debug-types -c -o /home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/whrlpool/wp_block.o ../deps/openssl/openssl/crypto/whrlpool/wp_block.c | make[1]: execvp: printf: Argument list too long I get the second problem when I run from: /home/ulf/projects/ICU/Angstrom/setup-scripts/ When I install Angstrom in /home/icu/v2012.12 I do not see the problem. --- Have tried recompiling my kernel changing include/linux/binfmts.h # define MAX_ARG_PAGES32 # define MAX_ARG_PAGES64 based on something I found on Internet, to no avail. Checking a little bit more, I see it looks like: #ifdef CONFIG_MMU ... #else # define MAX_ARG_PAGES64 struct page *page[MAX_ARG_PAGES]; #endif CONFIG_MMU is set, so the change is in part of the code which is not used Maybe there should be some kind of warning about how deep in the directory structure Angstrom can be. --- The resulting kernel/filesystem will run on the Beagleboard Black. Anyone knows what to change to increase the argument area on linux-3.2.x? BR Ulf Samuelsson ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [OE-core] Problems when building Angstrom master 1.3 1.4 for Beagleboard Black
On 2013-10-11 16:58, Koen Kooi wrote: Op 11 okt. 2013, om 16:32 heeft Ulf Samuelsson angstrom-...@emagii.com het volgende geschreven: Have tried out building Angstrom for Beaglebone Black on a Quad-Core i7/Ubuntu 12.04 i386 with: I strongly recommend ditching ubuntu and installing linux instead. I don't know what causes it, but switching to debian, arch, gentoo, fedora, opensuse or anything else not ubuntu based gets rid off all problems with builds not working, not booting, etc. OK, after installing 12.04LTS I have to 1. left-click (hold) 2. alt (hold) 3. right click just to add an item to the panel, I guess they are trying to prove that Ubuntu One is superior to gnome, by making gnome successively worse. so I am quite pissed of with Ubuntu Getting a dual Xeon 6-core next week, so I'll wait until then, but that is not going to be exposed to Ubuntu ever... BR Ulf PARALLEL_MAKE = -j8 BB_NUMBER_THREADS = 8 I bitbake cloud9-gnome-image RESULTS: * remotes/origin/angstrom-v2013.06-yocto1.4commit 246357a1cc4977683ada564d38218e837ac615e3 image builds but does not boot. * remotes/origin/angstrom-v2012.12-yocto1.3commit 01984cc460acfe5e7d5bab4feeb0888d5c6fe77f image builds but does not boot. * origin/master commit 7a3b004f7bfa24ea54b0da78bd80e4dd7839321d Build fails on two issues. 1.libxklavier compile fails. | xklavier.c: In function 'xkl_engine_class_init': | xklavier.c:846:8: error: 'XKL_TYPE_ENGINE_FEATURES' undeclared (first use in this function) ... Summary: 1 task failed: /home/ulf/projects/ICU/Angstrom/setup-scripts/sources/meta-openembedded/meta-gnome/recipes-gnome/libxklavier/libxklavier_5.0.bb, do_compile Did bitbake -c cleansstate libxklavier and restarted, and then it continued without problem, so there seem to be a dependency problem. 2.nodejs compiles fails with error: | arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/beaglebone '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DL_ENDIAN' '-DOPENSSL_THREADS' '-DPURIFY' '-D_REENTRANT' '-DOPENSSL_NO_DTLS1' '-DOPENSSL_NO_SOCK' '-DOPENSSL_NO_DGRAM' '-DOPENSSL_NO_GOST' '-DOPENSSL_NO_HW_PADLOCK' '-DOPENSSL_NO_ASM' '-DENGINESDIR=/dev/null' '-DOPENSSLDIR=/etc/ssl' '-DTERMIOS' -I../deps/openssl -I../deps/openssl/openssl -I../deps/openssl/openssl/crypto -I../deps/openssl/openssl/crypto/asn1 -I../deps/openssl/openssl/crypto/evp -I../deps/openssl/openssl/crypto/store -I../deps/openssl/openssl/include -I../deps/openssl/config/android -Wall -pthread -O2 -fno-strict-aliasing -fno-tree-vrp -MMD -MF /home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.2 2-r0/node-v0.8.22/out/Release/.deps//home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/whrlpool/wp_block.o.d.raw -O2 -pipe -g -feliminate-unused-debug-types -c -o /home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/whrlpool/wp_block.o ../deps/openssl/openssl/crypto/whrlpool/wp_block.c | make[1]: execvp: printf: Argument list too long I get the second problem when I run from: /home/ulf/projects/ICU/Angstrom/setup-scripts/ When I install Angstrom in /home/icu/v2012.12 I do not see the problem. --- Have tried recompiling my kernel changing include/linux/binfmts.h # define MAX_ARG_PAGES32 # define MAX_ARG_PAGES64 based on something I found on Internet, to no avail. Checking a little bit more, I see it looks like: #ifdef CONFIG_MMU ... #else # define MAX_ARG_PAGES64 struct page *page[MAX_ARG_PAGES]; #endif CONFIG_MMU is set, so the change is in part of the code which is not used Maybe there should be some kind of warning about how deep in the directory structure Angstrom can be. --- The resulting kernel/filesystem will run on the Beagleboard Black. Anyone knows what to change to increase the argument area on linux-3.2.x? BR Ulf Samuelsson ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Need help building kernel, toolchain and rootfs for AT91
On 2013-09-21 21:29, Jim Norton wrote: NOTE: Willing to pay $200 USD via PayPal for specific detailed help/instructions. Hello Everybody, I've used the search engines. However, for buildroot, OE and Angstrom I can find generic instructions for using the systems, however it is unclear to me how to build the various parts ( kernel, toolchain, filesystem ) specifically for AT91SAM9260. I'm having a hard time putting all of the pieces together. I was able to build a root filesystem using buildroot, but I *don't* want to use uClibc. I am willing to pay somebody via PayPal $200 USD for detailed instructions on how to build the kernel, toolchain and root filesystem for AT91SAM9260 ( Olimex SAM9-L9260 ) using Angstrom/OE. The reason I am willing to pay is that I am working on project and I don't have a lot of time to figure this all out. I'd love to solve it on my own, but I am on a deadline Anybody willing to help me out? Sure. You can contact me directly on ulf at emagii dot com BR Ulf Samuelsson Regards, notronrj ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Narcissus update to v2012.12, please read
22 mar 2013 kl. 11:35 skrev Koen Kooi k...@dominion.thruhere.net: Op 21 mrt. 2013, om 18:33 heeft Nicolas Aguirre aguirre.nico...@gmail.com het volgende geschreven: Hi, I'm currently working on an home automation project (calaos), which uses angstrom and oe-core + my own recipes [1][2]. I maitains a set of machine for this project : n450 cubieboard mele a1000/2000 cubox olinuxino-a13 rasberry-pi mele a1000/2000, cubieboard and olinuxino-a13 is based on meta-allwinner [3] cubox is based on meta-cubox [4] I'm using the danny branch for all my layers, so i guess i can help here. I attached the patch for the support of allwinner and cubox. I will run a build for mele/cubieboard/olinuxino and cubox during the night and tomorrow to check that everything build correctly with setup-scripts. Same comment I made a few months ago: DEFAULTTUNE=cortexa8hf-neon Hardfloat/softfp t is a DISTRO decision, not a machine decision, so I can't add meta-allwinner and meta-cubox to Angstrom with that setting in the machine configs. Does that mean that Angstrom cannot be used for ARM9 nowadays? Cortex-A5 without Neon? Best Regards Ulf Samuelsson regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH 1/3] Allow multiple environment files with clean option + HOSTCORES
That reports the number of threads, so if the core supports Hyperthreading
you get 2 x Cores.
PARALLEL_MAKE would be -j12 on my Core i7 980X.
OFF-TOPIC (sorry)
This also shows me a problem on my machine Core i7 980X
with 6 cores / 12 threads, but /proc/cpuinfo reports 8 threads
on Ubuntu 11.04 32 bit with a recompiled kernel.
When running 11.04 64 bit kernel (vanilla) it reports 12 threads.
Anyone knows if this is 32 bit kernel specific?
The change in .config is really small.
Best Regards
Ulf Samuelsson
9 jun 2012 kl. 18:26 skrev Khem Raj raj.k...@gmail.com:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/9/2012 3:51 AM, u...@emagii.com wrote:
+echo export HOSTCORES=`cat /proc/cpuinfo | grep \cpu cores\
| tail --lines=1 | sed -e \s/cpu cores\t: //g\`
${OE_ENV_FILE}
I think this only gives info about how many cores are on same socket.
if you have two sockets then it may not be reporting the right thing
what you could do is
export HOSTCORES=`cat /proc/cpuinfo | grep '^processor' | wc -l`
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/TeUAACgkQuwUzVZGdMxTasgCfXRe8lUIrSMDuZD0KQmR5jwYf
h3YAniyYFJatZsuL6aEwyYQ++W6nRrfX
=qDIE
-END PGP SIGNATURE-
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH 1/2] conf/local.conf: Add fs, OE_CORES, PREMIRRORS
Best Regards
Ulf Samuelsson
u...@emagii.com
+46 (722) 427 437
6 jun 2012 kl. 10:50 skrev Koen Kooi k...@dominion.thruhere.net:
Op 5 jun. 2012, om 07:58 heeft u...@emagii.com het volgende geschreven:
From: Ulf Samuelsson u...@emagii.com
Build jffs2 and ubifs as well as tar.bz2
Add OE_CORES env variable for parallellity
Add some PREMIRRORS
Signed-off-by: Ulf Samuelsson u...@emagii.com
---
conf/local.conf | 37 ++---
1 files changed, 34 insertions(+), 3 deletions(-)
diff --git a/conf/local.conf b/conf/local.conf
index 2477a90..77a6350 100644
--- a/conf/local.conf
+++ b/conf/local.conf
@@ -8,13 +8,15 @@ INHERIT += rm_work
BBMASK =
# What kind of images do we want?
-IMAGE_FSTYPES += tar.bz2
+IMAGE_FSTYPES += tar.bz2 jffs2 ubi
This is too specific for generic setupscripts
They help newbies.
Saw a recent post on the mailing list wondering what to do to get jffs2 built.
The cost is some Hard Disk space and they are quite popular alternatives.
# Make use of SMP:
# PARALLEL_MAKE specifies how many concurrent compiler threads are spawned
per bitbake process
# BB_NUMBER_THREADS specifies how many concurrent bitbake tasks will be run
-PARALLEL_MAKE = -j2
-BB_NUMBER_THREADS = 2
+OE_CORES ?= 4
+PARALLEL_MAKE = -j
+PARALLEL_MAKE+= ${OE_CORES}
+BB_NUMBER_THREADS ?= ${OE_CORES}
And that name is too confusing.
How about HOST_CPU_CORES ?
DISTRO = angstrom-v2012.05
@@ -43,3 +45,32 @@ PATCHRESOLVE = noop
#SSTATE_MIRRORS ?= \
#file://.* http://dominion.thruhere.net/angstrom/sstate-mirror/ \n
+PREMIRRORS_append = \
+bzr://.*/.* http://pokylinux.org/sources/ \n \
+cvs://.*/.* http://pokylinux.org/sources/ \n \
+git://.*/.* http://pokylinux.org/sources/ \n \
+hg://.*/.*http://pokylinux.org/sources/ \n \
+osc://.*/.* http://pokylinux.org/sources/ \n \
+p4://.*/.*http://pokylinux.org/sources/ \n \
+svk://.*/.* http://pokylinux.org/sources/ \n \
+svn://.*/.* http://pokylinux.org/sources/ \n \
+bzr://.*/.* http://autobuilder.pokylinux.org/sources/ \n \
+cvs://.*/.* http://autobuilder.pokylinux.org/sources/ \n \
+git://.*/.* http://autobuilder.pokylinux.org/sources/ \n \
+hg://.*/.*http://autobuilder.pokylinux.org/sources/ \n \
+osc://.*/.* http://autobuilder.pokylinux.org/sources/ \n \
+p4://.*/.*http://autobuilder.pokylinux.org/sources/ \n \
+svk://.*/.* http://autobuilder.pokylinux.org/sources/ \n \
+svn://.*/.* http://autobuilder.pokylinux.org/sources/ \n
+
+MIRRORS += \
+${KERNELORG_MIRROR}ftp://ftp.sunet.se/pub/Linux/kernel.org \n \
+
+MIRRORS_append = \
+ftp://.*/.* http://pokylinux.org/sources/ \n \
+http://.*/.*http://pokylinux.org/sources/ \n \
+https://.*/.* http://pokylinux.org/sources/ \n \
+ftp://.*/.* http://autobuilder.pokylinux.org/sources/ \n \
+http://.*/.* http://autobuilder.pokylinux.org/sources/ \n \
+https://.*/.*http://autobuilder.pokylinux.org/sources/ \n \
And that belongs in the meta-angstrom layer.
OK.
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH 1/2] conf/local.conf: Add fs, OE_CORES, PREMIRRORS
HOSTCORES
Best Regards
Ulf Samuelsson
u...@emagii.com
+46 (722) 427 437
6 jun 2012 kl. 11:25 skrev Koen Kooi k...@dominion.thruhere.net:
Op 6 jun. 2012, om 11:16 heeft Ulf Samuelsson het volgende geschreven:
# Make use of SMP:
# PARALLEL_MAKE specifies how many concurrent compiler threads are
spawned per bitbake process
# BB_NUMBER_THREADS specifies how many concurrent bitbake tasks will be
run
-PARALLEL_MAKE = -j2
-BB_NUMBER_THREADS = 2
+OE_CORES ?= 4
+PARALLEL_MAKE = -j
+PARALLEL_MAKE+= ${OE_CORES}
+BB_NUMBER_THREADS ?= ${OE_CORES}
And that name is too confusing.
How about HOST_CPU_CORES ?
Better, but still too much underscores, the trend is to avoid then in
variable names to reduce parse time.
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH 2/2] Create local environment file
On 2012-06-05 18:12, Denys Dmytriyenko wrote:
On Tue, Jun 05, 2012 at 07:58:15AM +0200, u...@emagii.com wrote:
From: Ulf Samuelssonu...@emagii.com
Signed-off-by: Ulf Samuelssonu...@emagii.com
---
oebb.sh | 27 ---
1 files changed, 20 insertions(+), 7 deletions(-)
diff --git a/oebb.sh b/oebb.sh
index d71718a..85b60dc 100755
--- a/oebb.sh
+++ b/oebb.sh
@@ -37,6 +37,19 @@ OE_BASE=${PWD}
BASE_VERSION=5
OE_ENV_FILE=~/.oe/environment-angstromv2012.05
+BASE_DIR=`basename $OE_BASE`
+ANGSTROM=`echo $BASE_DIR | grep Angstrom`
+
+if [ $BASE_DIR == setup-scripts ] ; then
+ PROJECT_DIR=`dirname$OE_BASE`
+else
+ PROJECT_DIR=$OE_BASE
+fi
+PROJECT=`basename $PROJECT_DIR | sed -e s/-Angstrom-Distribution//g`
+
+# incremement this to force recreation of config files
+OE_ENV_FILE=~/.oe/env-$PROJECT.sh
+
if ! git help log | grep -q no-abbrev ; then
echo Your installed version of git is too old, it lacks --no-abbrev. Please
install 1.7.6 or newer
exit 1
@@ -159,7 +172,7 @@ else
# Make sure Bitbake doesn't filter out the following variables from our
# environment.
#--
-export BB_ENV_EXTRAWHITE=MACHINE DISTRO TCLIBC TCMODE GIT_PROXY_COMMAND
http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK
BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS
+export BB_ENV_EXTRAWHITE=MACHINE DISTRO TCLIBC TCMODE GIT_PROXY_COMMAND
http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK
BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS OE_CORES
echo export BB_ENV_EXTRAWHITE=\${BB_ENV_EXTRAWHITE}\ ${OE_ENV_FILE}
@@ -191,14 +204,15 @@ else
echo export BBPATH=\${BBPATH}\ ${OE_ENV_FILE}
#--
-# Look for dash
+# Reconfigure dash
#--
if [ $(readlink /bin/sh) = dash ] ; then
- echo /bin/sh is a symlink to dash, please point it to bash instead
-exit 1
+sudo aptitude install expect -y
Huh? What's that? What is aptitude?
http://en.wikipedia.org/wiki/Aptitude_%28software%29
+expect -c 'spawn sudo dpkg-reconfigure -freadline dash; send n\n;
interact;'
And this? What's dpkg-reconfigure?
It allows to reconfigure (at least on Ubuntu).
Maybe it is a bad idea, since thid fix is using non standard packages.
I have a script which loads Ubuntu with evertyhing I need
The important part of the patch is to have the environment file
in the setup-scripts directory as well, and to have a name
which reflects the projects, so several projects can coexist.
BR
Ulf
fi
-echo There now is a sourceable script in ~/.oe/enviroment. You can do '.
${OE_ENV_FILE}' and run 'bitbake something' without using $0 as wrapper
+cp ${OE_ENV_FILE} .
+echo There now is a sourceable script in ~/.oe. You can do '. ${OE_ENV_FILE}'
and run 'bitbake something' without using $0 as wrapper
fi # if -e ${OE_ENV_FILE}
if ! [ -e ${OE_BUILD_DIR}/conf/site.conf ] ; then
@@ -454,8 +468,7 @@ echoNot recommended, but also possible:
echo$0 bitbakebitbake target
echoIt is recommended to do '. ${OE_ENV_FILE}' and run 'bitbake
something' inside ${BUILDDIR} without using oebb.sh as wrapper
echo
-echo You must invoke \$0 configmachine\ and then \$0 update\ prior
-echo to your first bitbake command
+echo You must invoke \$0 configmachine\ and then \$0 update\ prior to your
first bitbake command
echo
echo Themachine argument can be one of the following
echobeagleboard: BeagleBoard
--
1.7.4.1
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] quilt-native do_configure bombs due to unrecognizwd options (--disable-silent-rules, --disable-dependency-tracking)
On 2012-05-05 17:51, Khem Raj wrote: On Sat, May 5, 2012 at 8:17 AM, Ulf Samuelssonangstrom-...@emagii.com wrote: Sorry, didn't look close enough. Looks like ccache gcc --version fails during configure. gcc --version works. !! seems your build host problem disable ccache if you want to workaround it Yes, I checked up the system, and found ccache-2.4 in an old cross-compiler, I recently installed. This was used, instead of the normal host ccache. Removed the path and now the ccache gcc --version command works. BR Ulf Samuelsson ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] quilt-native do_configure bombs due to unrecognizwd options (--disable-silent-rules, --disable-dependency-tracking)
On 2012-05-05 00:41, Ulf Samuelsson wrote: Downloaded a fresh version of the Angstrom setup scripts today, and it fails already when building pseudo. quilt-native.configure bombs with the following error message. configure: WARNING: unrecognized options: --disable-silent-rules, --disable-dependency-tracking Sorry, didn't look close enough. Looks like ccache gcc --version fails during configure. gcc --version works. !! BR Ulf Samuelsson Past mifhnight, so I wont investigate further today. Full log. NOTE: package quilt-native-0.51-r0: task do_configure: Started NOTE: package m4-native-1.4.16-r2: task do_fetch: Started ERROR: Function failed: do_configure (see /home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/temp/log.do_configure.7636 for further information) ERROR: Logfile of failure stored in: /home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/temp/log.do_configure.7636 Log data follows: | ERROR: Function failed: do_configure (see /home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/temp/log.do_configure.7636 for further information) | NOTE: Running /home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/quilt-0.51/configure --build=x86_64-linux --host=x86_64-linux --target=x86_64-linux --prefix=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr --exec_prefix=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr --bindir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/bin --sbindir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/sbin --libexecdir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/libexec --datadir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/share --sysconfdir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/etc --sharedstatedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/com --localstatedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/var --libdir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/lib --includedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include --oldincludedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include --infodir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/share/info --mandir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/share/man --disable-silent-rules --disable-dependency-tracking--disable-nls | configure: WARNING: unrecognized options: --disable-silent-rules, --disable-dependency-tracking | checking for x86_64-linux-gcc... ccache gcc | checking for C compiler default output file name... | configure: error: in `/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/quilt-0.51': | configure: error: C compiler cannot create executables | See `config.log' for more details. | ERROR: oe_runconf failed NOTE: package quilt-native-0.51-r0: task do_configure: Failed ERROR: Task 12 (/home/ulf/projects/Angstrom-Distribution/setup-scripts/sources/openembedded-core/meta/recipes-devtools/quilt/quilt-native_0.51.bb, do_configure) failed with exit code '1' Waiting for 1 running tasks to finish: 0: m4-native-1.4.16-r2 do_fetch (pid 7637) NOTE: package m4-native-1.4.16-r2: task do_fetch: Succeeded NOTE: Tasks Summary: Attempted 7 tasks of which 5 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/ulf/projects/Angstrom-Distribution/setup-scripts/sources/openembedded-core/meta/recipes-devtools/quilt/quilt-native_0.51.bb, do_configure Summary: There was 1 ERROR message shown, returning a non-zero exit code. ___ Angstrom-distro-devel mailing list Angstrom
[Angstrom-devel] quilt-native do_configure bombs due to unrecognizwd options (--disable-silent-rules, --disable-dependency-tracking)
Downloaded a fresh version of the Angstrom setup scripts today, and it fails already when building pseudo. quilt-native.configure bombs with the following error message. configure: WARNING: unrecognized options: --disable-silent-rules, --disable-dependency-tracking Past mifhnight, so I wont investigate further today. Full log. NOTE: package quilt-native-0.51-r0: task do_configure: Started NOTE: package m4-native-1.4.16-r2: task do_fetch: Started ERROR: Function failed: do_configure (see /home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/temp/log.do_configure.7636 for further information) ERROR: Logfile of failure stored in: /home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/temp/log.do_configure.7636 Log data follows: | ERROR: Function failed: do_configure (see /home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/temp/log.do_configure.7636 for further information) | NOTE: Running /home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/quilt-0.51/configure --build=x86_64-linux --host=x86_64-linux --target=x86_64-linux --prefix=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr --exec_prefix=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr --bindir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/bin --sbindir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/sbin --libexecdir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/libexec --datadir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/share --sysconfdir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/etc --sharedstatedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/com --localstatedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/var --libdir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/lib --includedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include --oldincludedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include --infodir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/share/info --mandir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/share/man --disable-silent-rules --disable-dependency-tracking--disable-nls | configure: WARNING: unrecognized options: --disable-silent-rules, --disable-dependency-tracking | checking for x86_64-linux-gcc... ccache gcc | checking for C compiler default output file name... | configure: error: in `/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/quilt-0.51': | configure: error: C compiler cannot create executables | See `config.log' for more details. | ERROR: oe_runconf failed NOTE: package quilt-native-0.51-r0: task do_configure: Failed ERROR: Task 12 (/home/ulf/projects/Angstrom-Distribution/setup-scripts/sources/openembedded-core/meta/recipes-devtools/quilt/quilt-native_0.51.bb, do_configure) failed with exit code '1' Waiting for 1 running tasks to finish: 0: m4-native-1.4.16-r2 do_fetch (pid 7637) NOTE: package m4-native-1.4.16-r2: task do_fetch: Succeeded NOTE: Tasks Summary: Attempted 7 tasks of which 5 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/ulf/projects/Angstrom-Distribution/setup-scripts/sources/openembedded-core/meta/recipes-devtools/quilt/quilt-native_0.51.bb, do_configure Summary: There was 1 ERROR message shown, returning a non-zero exit code. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Error deploying net-at91sam9-image for SAM9G25
Any progress on this?
Just ran into he same problem.
Best Regards
Ulf Samuelsson
4 apr 2012 kl. 15:13 skrev Bryan Evenson beven...@melinkcorp.com:
I'm still having this issue. From what I can gather, at one point the
installation of hid2hci switched from udev to bluez4. However, I can't tell
from the OE logs at what point this happened and which versions of udev and
bluez4 do what. I can tell you that my image is building bluez4_4.95.bb and
that it lists preferred version info for udev as:
PREFERRED_VERSION_udev= 165
PREFERRED_VERSION_udev_libc-uclibc = 141
UDEV_GE_141 = 1
I also see in the bluez4_4.95.bb file that there is a variable that is set as:
# Not all distros have a recent enough udev
BTUDEV = --disable-udevrules
BTUDEV_angstrom = --enable-udevrules
BTUDEV_shr = --enable-udevrules
EXTRA_OECONF += ${BTUDEV}
The start of my build configuration says that DISTRO = angstrom, so I'm
assuming that BTUDEV is getting set to --enable-udevruels. Is this what I
want? Anyone else having similar issues with the Angstrom build on the
2011.03-maintenance branch?
Thanks,
Bryan
-Original Message-
From: angstrom-distro-devel-boun...@linuxtogo.org
[mailto:angstrom-distro-devel-boun...@linuxtogo.org] On Behalf Of Bryan
Evenson
Sent: Tuesday, March 27, 2012 11:18 AM
To: angstrom-distro-devel@linuxtogo.org
Subject: [Angstrom-devel] Error deploying net-at91sam9-image for SAM9G25
Hello all,
I'm in the process of building Angstrom for the first time for my SAM9G25-EK.
I've been following the instructions here
http://www.at91.com/linux4sam/bin/view/Linux4SAM/BuildAngstrom_9x5 and have
been able to successfully build the base image (bitbake base-image). Making
the console image (bitbake net-at91sam9-image) works fine until the final
deploy steps. Here is the error message that I am seeing:
| * resolve_conffiles: Existing conffile
/media/sda3/stuff/tmp/rootfs/net-at91sam9-image/etc/device_table is different
from the conffile in the new package. The new conffile will be placed at
/media/sda3/stuff/tmp/rootfs/net-at91sam9-image/etc/device_table-opkg.
| * check_data_file_clashes: Package udev wants to install file
/media/sda3/stuff/tmp/rootfs/net-at91sam9-image/lib/udev/hid2hci
| But that file is already provided by package * bluez4
| * opkg_install_cmd: Cannot install package udev.
NOTE: package net-at91sam9-image-1.0-r0: task do_rootfs: Failed
ERROR: Function 'do_rootfs' failed (see
/media/sda3/stuff/tmp/work/at91sam9x5ek-angstrom-linux-gnueabi/net-at91sam9-image-1.0-r0/temp/log.do_rootfs.4503
for further information)
ERROR: Task 14
(/media/sda3/stuff/oe_at91sam/recipes/images/net-at91sam9-image.bb,
do_rootfs) failed with exit code '1'
ERROR: '/media/sda3/stuff/oe_at91sam/recipes/images/net-at91sam9-image.bb'
failed
So it appears there is some conflict between bluez4 and udev with the file
hid2hci. However, I haven't found any more description than that. I'm
guessing this means that both packages are trying to provide the same file,
but I'm not sure which one should win in this case. Has anyone else had
similar issues?
If it helps, here's the build configuration information as it appeared near
the start of the build:
Build Configuration:
BB_VERSION= 1.12.0
METADATA_BRANCH = 2011.03-maintenance
METADATA_REVISION = ec639a6
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = at91sam9x5ek
DISTRO= angstrom
DISTRO_VERSION= v20120327
TARGET_FPU= soft
Any ideas on how to fix this conflict?
Thanks,
Bryan
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
You can at time rlogin even if you do not get a prompt. also, NFS mounting will give you access to logs onthe NFS host. Best Regards Ulf Samuelsson 4 mar 2012 kl. 13:48 skrev Gary Thomas g...@mlbassoc.com: All of the recent images I've built (for beaglebone at least) fail on boot with these messages: Starting Journal Service... Failed to start Journal Service [FAILED] See 'systemctl status systemd-journald.service' for details. Dependency failed. Aborted start of Getty on tty1 [ ABORT] Dependency failed. Aborted start of Serial Getty on ttyO0 [ ABORT] Since this is a very early-on failure, nothing runs and I can't get in to run the status command to figure out what's wrong. Perhaps there is some way to get more verbose output to the console? I could edit some config file, etc, offline an try another boot. This build was for systemd-image, from a 100% scratch setup, as of 2012-03-02 1500 GMT OE Build Configuration: BB_VERSION= 1.15.1 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beaglebone DISTRO= angstrom DISTRO_VERSION= v2012.03-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:2129eed920364abcc4f3f72d395333a041634e26 meta-oe meta-efl meta-gpe meta-gnome meta-xfce meta-initramfs= master:fdff8697ea2db6254d26510adb7d11e6352d950f meta-opie = master:efa3892b20a4ef80274e56e5633ebd62c16f9731 meta-java = master:d430de31c167cd264be74a1d82af4b732bb915dd meta-mozilla = master:5737d9fa26a632a27b2aa760c0d01190f0a17d0e meta-ti = master:020b6f893d13e36bccd7a2d8e6a0e6ab5e602450 meta-efikamx = master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d meta-nslu2= master:3d9fc951b05b4df476374b6fc3085ebac7f293ee meta-htc meta-nokia meta-openmoko meta-palm = master:cda19686a2a3573ce50c86733c3469d926124995 meta-handheld = master:fa1e6dcb524eb7ed29a6cd971a150d35c31e96e7 meta-intel meta-sugarbay meta-crownbay meta-emenlow meta-fishriver meta-jasperforest meta-n450 = master:df18b721f86f0737c0f302e49b27ea232c70e683 meta = master:b24d4bcde21b013e48eaffea5f3a70d8b1df1047 -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] UNSUBSCRIBE
Stop acting like a Moron! If you are subscribed to a list, by mistake or because someone played a nasty trick on you, then follow the procedure to unsubscribe instead of botherng other people with your SPAM!!! Best Regards Ulf Samuelsson 6 mar 2012 kl. 02:07 skrev John Babrick johnbabr...@hughes.net: UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE
Re: [Angstrom-devel] build broken, ca-certificates no longer available, patch attached
There is already a patch submitted to the mailing list since one week. Best Regards Ulf Samuelsson 4 mar 2012 kl. 10:01 skrev Koen Kooi k...@dominion.thruhere.net: Op 3 mrt. 2012, om 22:08 heeft Norman Schleicher het volgende geschreven: On 03/03/2012 09:55 PM, Koen Kooi wrote: Op 3 mrt. 2012, om 21:49 heeft Norman Schleicher het volgende geschreven: hello, old ca certificates no longer available, ERROR: Task 3117 (/var/lib/jenkins/jobs/pandaboard-angstrom/workspace/setup-scripts/sources/meta-openembedded/meta-oe/recipes-support/ca-certificates/ca-certificates_20111211.bb, do_fetch) failed with exit code '1' please test and apply patch (meta-oe). Can you please submit it as laid out in the meta-oe README https://github.com/openembedded/meta-oe/tree/master/meta-oe ? Hope its now correct, would be nice to know what was wrong. The mailing list for one :) ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Can't build Angstrom for PandaBoard
You have defined a MACHINE=pandaboard, and this machine needs to have its kernel .config in .../recipes-kernel/linux/linux-3.0.1/pandaboard/defconfig Best Regards Ulf Samuelsson u...@emagii.com 29 feb 2012 kl. 16:08 skrev Gary Thomas g...@mlbassoc.com: OE Build Configuration: BB_VERSION= 1.15.1 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = pandaboard DISTRO= angstrom DISTRO_VERSION= v2012.02-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:5ee94f7916e074cfea6e95301955a04dd9ed meta-oe meta-efl meta-gpe meta-gnome meta-xfce meta-initramfs= master:3d15d096b6cd691d9b7e7b00c44498b73e9661b5 meta-opie = master:efa3892b20a4ef80274e56e5633ebd62c16f9731 meta-java = master:9c6d9367eeada083aacf182da628238993ca5100 meta-ti = master:c44b242d8509738df60a7cbb57f9a5f27e103fad meta-efikamx = master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d meta-nslu2= master:3d9fc951b05b4df476374b6fc3085ebac7f293ee meta-htc meta-nokia meta-openmoko meta-palm = master:1af999cd2ce27fe06225336a5e62a262635968e9 meta-handheld = master:8e568e525e97befa2d74937c344a3578a252d97c meta-intel meta-sugarbay meta-crownbay meta-emenlow meta-fishriver meta-jasperforest meta-n450 = master:df18b721f86f0737c0f302e49b27ea232c70e683 meta = master:17f2d5d70ad323cea4fb149154bc38844661fa3a ERROR: Logfile of failure stored in: /local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work/pandaboard-angstrom-linux-gnueabi/linux-3.0.1-r0/temp/log.do_fetch.8534 Log data follows: | DEBUG: Trying PREMIRRORS | DEBUG: Trying Upstream | ERROR: Function failed: Fetcher failure for URL: 'file://defconfig'. Unable to fetch URL from any source. NOTE: package linux-3.0.1-r0: task do_fetch: Failed Any ideas where to get this file? Thanks -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] xM rev C not booting and serial console only shows60
Yes, you need to check that the number of cylinders and heads are compatible with the bootROM of the part in question. These are available with the extended fdisk command set. Other problems, I have seen with SD card boot is that U-boot is very sensitive to the contents of a FAT file system. If U-boot 2009.11 sees a FAT file system where there is a hidden file starting with a '.', it will bomb. I.E: if .Trash exists on the D card, it won't boot. There are other characterss which are unpopular, like ''. If you have a booting sd card, and then copy a file with an illegal filename, then remove it, it still won't boot since you just copied The file to the .Trash directory - bummer ! Best Regards Ulf Samuelsson u...@emagii.com +46 (722) 427 437 14 feb 2012 kl. 09:30 skrev Hauser, Wolfgang (external) wolfgang.hauser.exter...@cassidian.com: Hello Robert P. J. Day, it may be I use the wrong formatting and partitioning parameters, or there is some restriction in the size of the FAT32 partition. I create the SD-cards according to the instructions angstrom distribution provides. It works sometimes and sometimes it's not working. I always get problems if the FAT32 partition is bigger then 1G. Can you please provide your partitioning and formatting parameters ? And what system do you use for preparing the SD cards ? Regards Wolfgang -Ursprüngliche Nachricht- Von: angstrom-distro-devel-boun...@linuxtogo.org [mailto:angstrom-distro-devel-boun...@linuxtogo.org] Im Auftrag von Robert P. J. Day Gesendet: Montag, 13. Februar 2012 18:48 An: Discussion of the angstrom distribution development Betreff: Re: [Angstrom-devel] xM rev C not booting and serial console only shows60 On Mon, 13 Feb 2012, Hauser, Wolfgang (external) wrote: Hello, I got this ERROR too, but with a newly created SD-card. What I've done, is to copy the contents of the FAT 32 partition, reformat it from a XP machine and copy back the content. !! Starting with MLO !! and then the rest. It seems that the FAT32 Partition often make problems when it is manipulated from a linux system. May be the loader chip of the beagleboard is a bit restrictive. i find that hard to believe. i've formatted/reformatted *countless* SD cards from linux and they boot on my xM rev C just fine. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Improving boot time of first boot (Precompling icon-theme.cache files).
I have built an image based on Angstom setup scripts with my own layer for an AT91 ARM9 @ 400 MHz. The image is based on systemd-GNOME-image but I have added some extra applications like mplayer and fbv and the image will also include some pictures/music/movies to test out. Have yet to test without nfs. the only boot parameters I have is root=/dev/nfs rw rootdir=... I had a boottime problem some time ago and IIRC the fix was to put tmpfs in RAM, so that has already been implemented before this problem occured. Discussed another boot problem with Koen, and he pointed me to an email with recommended kernel configurations, have now impelemented this, but ony booted that once. had some garbled USART output,and I didn't measure the boot time. Will do that later this week. Best Regards Ulf Samuelsson u...@emagii.com +46 (722) 427 437 6 feb 2012 kl. 16:23 skrev Khem Raj raj.k...@gmail.com: On Sun, Feb 5, 2012 at 11:35 PM, Ulf Samuelsson angstrom-...@emagii.com wrote: When I first load a system: * built using Angstrom on top of OE-Core * File system NFS mounted. it takes about 20 minutes before the boot completes. hmm. How does it go from non nfs mounted rfs. what is your system specification. what options do you use to mount nfs ? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Improving boot time of first boot (Precompling icon-theme.cache files).
When I first load a system: * built using Angstrom on top of OE-Core * File system NFS mounted. it takes about 20 minutes before the boot completes. I wanted to know why, so I initialized a git tree in the rootfs, and started doing git diff. At least for the first minutes, the only result was diff --git a/usr/share/icons/hicolor/icon-theme.cache b/usr/share/icons/hicolor/icon-theme.cache index 04fec3f..075046a 100644 Binary files a/usr/share/icons/hicolor/icon-theme.cache and b/usr/share/icons/hicolor/icon-theme.cache differ There are a lof of icon directories, so I suspect that the lion's part of the long first boot time is due to creating this cache. It looks to me like a recipe to update /usr/share/icons/*/icon-theme.cache in the generated root fs would be good rather than having the much slower target do it. --- There are alredy such files in the root fs, but when I compare what the size of /usr/share/icons/hicolor/icon-theme.cache in the tarball, with the file after the boot, it has grown from 64 kB to close to 1 MB. Apparently running /usr/bin/gtk-update-icon-cache will update the icon-theme.cache file. Checked the sources directory of Angstrom, and there are only a few recipes to generate icon-themes: ./meta-smartphone/meta-shr/recipes-shr/shr/icon-theme-neo_git.bb ./meta-angstrom/recipes-tweaks/themes/angstrom-gnome-icon-theme-enable.bb ./meta-openembedded/meta-gnome/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb ./meta-openembedded/meta-xfce/recipes-art/xfce4-icon-theme/xfce4-icon-theme_4.4.3.bb ./openembedded-core/meta/recipes-sato/sato-icon-theme/sato-icon-theme_0.4.1.bb ./openembedded-core/meta/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb ./openembedded-core/meta/recipes-gnome/gnome/gnome-icon-theme_2.31.0.bb Looked at meta-openembedded/meta-gnome/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb and found no trace of any icon-theme generation, but there still appears to be a small one there Looking through the file system of an image derived from systemd-GNOME-image I found -rw-r--r-- 1 root root 137204 2012-02-06 00:06 Crux/icon-theme.cache -rw-r--r-- 1 root root 53067356 2012-02-06 00:07 gnome/icon-theme.cache -rw-r--r-- 1 root root 972016 2012-02-06 00:07 hicolor/icon-theme.cache -rw-r--r-- 1 root root 1444280 2012-02-06 00:06 HighContrastLargePrint/icon-theme.cache -rw-r--r-- 1 root root 1661336 2012-02-06 00:06 HighContrastLargePrintInverse/icon-theme.cache -rw-r--r-- 1 root root 155260 2012-02-06 00:06 HighContrast-SVG/icon-theme.cache -rw-r--r-- 1 root root 5348 2012-02-06 00:06 LowContrastLargePrint/icon-theme.cache -rw-r--r-- 1 root root 5634892 2012-02-06 00:07 Mist/icon-theme.cache tried running gtk-update-icon-cache on hicolor, and it grew to about the same size as the one in a booted machine and this completed almost immediately.. If this is done, before the machine is booted, then the file system grows by ~63 MB, so programming the flash will take longer for each machine. What is uncertain to me, is if it is possible to cross-update the icon cache. Yet to be tested... Also, since the file system grows significantly, we need to think if this is OK or not. Any thoughts? Best Regards Ulf Samuelsson ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Angstrom setup scripts fails on meta-smartphone
Did a fresh install using the Angstrom setup scripts. MACHINE=qemuarm oebb.shconfigqemuarm This did not download meta-smartphone to sources, but it is still in conf/bblayers.conf DEBUG: LOAD /home/ulf/projects/OE_core/setup-scripts/sources/meta-smartphone/meta-htc/conf/layer.conf ERROR: Unable to parse /home/ulf/projects/OE_core/setup-scripts/sources/meta-smartphone/meta-htc/conf/layer.conf: [Errno 2] No such file or directory: '/home/ulf/projects/OE_core/setup-scripts/sources/meta-smartphone/meta-htc/conf/layer.conf' BTW: I don't read the Angstrom mailing list so I cross post! -- Best Regards Ulf Samuelsson eMagii ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] LAB-kernel-2.6.13-hh2 ??
Trying to adopt the Ångström distribution to the AT91SAM9263. Created some files conf/local/conf conf/machine/at91sam9263ek.conf packages/linux/linux-at91.bb packages/linux/linux-at91/at91sam9263ek/at91sam9263ek-linux-2.6.21.1.config packages/linux/linux-at91/kernel-patches-2.6.21.1/*.patch In local.conf I define MACHINE = at91sam9263ek DISTRO = angstrom-2007.1 TARGET_OS = linux-uclibc I assume that this means that local.conf will use my at91sam9263ek.conf file. In at91sam9263ek.conf I define: PREFERRED_PROVIDER_virtual/kernel = linux-at91 PREFERRED_PROVIDER_virtual/libqte2 = qte but this seems to be ignored, If I put the same thing in local.conf, it seems to work... Why? When I build, the system insist on using package/linux/LAB-kernel-2.6.13-hh2.bb Previously I have seen complaints about multiple provider of virtual/kernel I got rid of these by the PREFERRED_PROVIDER above but still LAB-kernel.. seems to be used. The LAB-kernel fails due to lack of version.h Why is the LAB kernel built? Can't seems to find a reference to it? NOTE: Handling BitBake files: / (4554/4554) [100 %] NOTE: Parsing finished. 3141 cached, 1206 parsed, 207 skipped, 0 masked. NOTE: build 200705171240: started OE Build Configuration: BB_VERSION = 1.8.2 OE_REVISION= e7f1b73351ab28d61011332ab47196f1dc6a1931 TARGET_ARCH= arm TARGET_OS = linux-gnueabi MACHINE= at91sam9263ek DISTRO = angstrom DISTRO_VERSION = test-20070517 TARGET_FPU = soft NOTE: Resolving missing task queue dependencies NOTE: preferred version 2.5 of glibc not available (for item virtual/arm-angstrom-linux-gnueabi-libc-for-gcc) NOTE: preferred version 1.1.1 of libx11-native not available (for item libx11-native) NOTE: Preparing Runqueue NOTE: Executing runqueue NOTE: Running task 1518 of 3946 (ID: 1426, /home/ulf/projects/OpenEmbedded/org.openembedded.dev/packages/linux/LAB-kernel_2.6.13-hh2.bb, do_unpack) NOTE: package LAB-kernel-2.6.13-hh2: started NOTE: package LAB-kernel-2.6.13-hh2-r0: task do_unpack: started NOTE: Unpacking /usr/local/install/downloads/linux.kernel26_anoncvs.handhelds.org_K2-6-13-hh2_.tar.gz to /home/ulf/projects/OpenEmbedded/build/tmp/work/at91sam9263ek-angstrom-linux-gnueabi/LAB-kernel-2.6.13-hh2-r0/ -- Best Regards, Ulf Samuelsson ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
