Re: [oe] Creating Rootfs images without packages
On Thu, Oct 13, 2011 at 3:37 AM, Ulf Samuelsson ulf_samuels...@telia.comwrote: On 2011-10-12 14:22, mgundes wrote: Hi, I think one of the big issue with OE is build time. It does everything for you, so that it takes too much times. I want to minimize build time and realized that OE creates ipkgs for almost every package. If there is a way to prevent creation of ipkgs it would be really good for me. In my opinion, it would be fine for other people too since usually rootfs directory is enough and ipkgs are not frequently used directly by developers. I have asked in freenode oe room but friends said there no way to do that in OE system. If there is no way to do that in current OE, do you plan to add as a feature? Thanks, Regards Question: What do youj mean by long build time. Building everything takes 1.5-2 hours. Doing an incremental build is much less. When I started, my laptop would take 42 hours to complete the build (Calculated, I gave up way before), but then I got a decent machine. If you consider 1.5 hours for the first build long, then you still have a problem If you can make it 30 minutes shorter, why wouldn't you try, it worths I think. I wondered and asked what can I do about it, that's it. -- Best Regards Ulf Samuelsson __**_ Openembedded-devel mailing list Openembedded-devel@lists.**openembedded.orgOpenembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/**cgi-bin/mailman/listinfo/**openembedded-develhttp://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel -- MahmutG ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Creating Rootfs images without packages
On Wed, Oct 12, 2011 at 11:46 PM, dashesy dash...@gmail.com wrote: On Wed, Oct 12, 2011 at 6:22 AM, mgundes mg...@hotmail.com wrote: Hi, I think one of the big issue with OE is build time. It does everything for you, so that it takes too much times. I want to minimize build time and realized that OE creates ipkgs for almost every package. If there is a way to prevent creation of ipkgs it would be really good for me. In my opinion, it would be fine for other people too since usually rootfs directory is enough and ipkgs are not frequently used directly by developers. Just as a suggestion: 1- You can start with a bare minimum rootfs then run it under qemu, or even on the board itself Then you can use opkg to download/upgrade from the repositories, or remove what you do not need. I guess this is the fastest method. I am thinking of putting together a build environment based on user-mode qemu and opkg. I use fedora's kickstart files to build my desktop rootfs. That would be great to have a similar approach using qemu and opkg. Specially for most people they do not need to compile the packages themselves and the repositories are enough, they only need to compile a few packages of their own. 2- You can only bitbake meta-toolchain to get a gcc with cross compilation capability, then use that to build any package that you want directly from sources without relying on OE. This is what I do myself right now, but you need to make sure the dependencies are met. If the dependencies of packages are correct and to the bare minimum required (which should becase or it should be filed as a bug), OE will be a better approach, it takes care of dependencies for you. The only problem I have is that OE is hugely customizable, and takes time to learn all different tricks to get exactly what I want in my rootfs. I am learning OE, for me I try to follow the mailing lists to learn non-out-dated information as the first thing I learned was to that most wikis are way outdated :) For example, is there a way not to compile any -dbg packages? I intuitively guess I need to set release in my local.conf but there is no easier way than trying it and check if -dbg packages are created or not. Thanks for suggestions dashesy, I am going to try to use external toolchain first. I think this will reduce much time if I achieve. I have asked in freenode oe room but friends said there no way to do that in OE system. If there is no way to do that in current OE, do you plan to add as a feature? Thanks, Regards -- MahmutG ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel dashesy ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel -- MahmutG ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Creating Rootfs images without packages
On Wed, 2011-10-12 at 15:22 +0300, mgundes wrote: I think one of the big issue with OE is build time. It does everything for you, so that it takes too much times. I want to minimize build time and realized that OE creates ipkgs for almost every package. If there is a way to prevent creation of ipkgs it would be really good for me. In my opinion, it would be fine for other people too since usually rootfs directory is enough and ipkgs are not frequently used directly by developers. If you want to eliminate ipk specifically then there is no problem: you can select package_rpm or package_tar or package_deb instead. If you want to eliminate the whole packaging step then this is rather more tricky and it's not really obvious that this would buy much. Do you have a proposal for how rootfs construction could be done in that case? p. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Creating Rootfs images without packages
On Thu, Oct 13, 2011 at 12:26 PM, Phil Blundell ph...@gnu.org wrote: On Wed, 2011-10-12 at 15:22 +0300, mgundes wrote: I think one of the big issue with OE is build time. It does everything for you, so that it takes too much times. I want to minimize build time and realized that OE creates ipkgs for almost every package. If there is a way to prevent creation of ipkgs it would be really good for me. In my opinion, it would be fine for other people too since usually rootfs directory is enough and ipkgs are not frequently used directly by developers. If you want to eliminate ipk specifically then there is no problem: you can select package_rpm or package_tar or package_deb instead. If you want to eliminate the whole packaging step then this is rather more tricky and it's not really obvious that this would buy much. Do you have a proposal for how rootfs construction could be done in that case? p. Hi Phil, I meant eliminating whole packages. Sometimes you think that it should be a better way even if you don't know the way. I am not expert on OE and unfortunately I don't have any proposal. I thought there may be or there should be a way to do but if founders and experts don't agree or say current is the best way to go, then everything is ok. May be later, when I learn OE good enough and if I figure out a way I surely share with OE team :) ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel -- MahmutG ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe] do_rootfs fails with networkmanager (was network-manager-applet) included
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Op 10-10-11 21:41, Andreas Müller schreef:
On Monday, October 10, 2011 12:19:53 PM Koen Kooi wrote:
Op 25-09-11 15:06, Andreas Müller schreef:
On Thursday, September 22, 2011 11:37:30 PM Andreas Müller wrote:
Hi
For my xfce-image ( lives in meta-angstrom/recipes-angstrom/images
) I want to make use of network-manager-applet which came in meta
oe few days ago.
It seems that as soon as I add network-manager-applet do_rootfs
fails with something like:
| Configuring openssh-sftp. | Configuring xf86-input-evdev. |
Configuring cpufrequtils. | Configuring systemd-compat-units. |
Configuring gvfsd-ftp. | Collected errors: | * extract_archive:
Cannot create symlink from ./var/run to 'volatile/run': File
exists. | + '[' '!' -z '' ']' | +
package_tryout_install_multilib_ipk | + multilib_tryout_dirs= | +
'[' '!' -z
/home/Superandy/tmp/oe-core-eglibc/work/overo-angstrom-linux-gnueabi/xfce-base-image-1.0-r0/multilib_check.py
']' | | ERROR: Function 'do_rootfs' failed (see
/home/Superandy/tmp/oe-core-eglibc/work/overo-angstrom-linux-gnueabi/xfce-base-image-1.0-r0/temp/log.do_rootfs.28313
for further information) NOTE: package xfce-base-image-1.0-r0: task
do_rootfs: Failed ERROR: Task 8
(/home/Superandy/data/oe-core/sources/meta-angstrom/recipes-angstrom/images/xfce-base-image.bb,
do_rootfs) failed with exit code '1' ERROR:
'/home/Superandy/data/oe-core/sources/meta-angstrom/recipes-angstrom/images/xfce-base-image.bb'
failed
Looked around a bit for this issue. As soon as there is
networkmanager included, do_rootfs fails with with something like
| Collected errors: | * extract_archive: Cannot create symlink from
./var/run to 'volatile/run': File exists.
In 'image'-folder of networkmanager I find a folder
'var/run/NetworkManager'. At do_rootfs this folder has moved to
'/var/volatile/run/NetworkManager' ( see
build/machine-angstrom-linux-gnueabi/image-1.0-r0/rootfs/var/volatile).
Seems as do_rootfs tries to setup a link 'var/run' where still a
(remaining) folder is present - or the transition from var/run -
var/volatile/run is somehow incomplete.
Any ideas how - or especially where to fix ( not only for
networkmanager I guess ). Maybe this is an oe-core issue but there no
networkmanager is available...
I've finally managed to reproduce this! I vaguely recall you finding
out some more details, could you please give a summary of your
finding?
regards,
koen
Hi Koen,
In historical order trying not to cause confusion this time :-)
1. I found a conflict between OE-Core creating /var/run-symlink by
'package.bbclass' together with 'meta/files/fs-perms.txt' on the one side
and angstrom 'base-files_3.0.14.bbappend' trying to create
/var/run-directory on the other side. I sent a patch [1] which fixed the
issue. Unfortunately I was a bit over-enthusiastic and sent the patch
together with [2] in a series. 2. On the first run, I recognized, that
the second part of the series caused missing directories and wrote that
in [3]. Here I meant to skip only the _second_ part of the series. 3.
You committed a workaround for /var/run issue [4]. 4. I asked if this is
neccessary in [5]. Your comment in the source ('we do not want that')
made me think it is mandatory to have /var/run as dir and I hoped to
learn the reason. 5. The broken do_rootfs still scared me in [6]. 6.
After none of the mails were responded, few days ago I decided to give
your workaround a try, reverted my patch and - surprise - did not get an
error on do_rootfs! So I thought I missed some magic and decided not to
cause further noise on that.
So I did some more digging and dumped the contents of all the ipks in deploy
and here are the packages (except basefiles) that touch /var/volatile/
bind_9.7.2-P3-r0_armv7a.ipk
drwxr-xr-x root/root 0 2011-10-13 00:35 ./var/volatile/
drwxr-xr-x root/root 0 2011-10-13 00:35 ./var/volatile/run/
lrwxrwxrwx root/root 0 2011-10-13 00:35 ./var/run - volatile/run
consolekit_0.4.5-r5_armv7a.ipk
lrwxrwxrwx root/root 0 2011-10-13 00:06 ./var/log - volatile/log
drwxr-xr-x root/root 0 2011-10-13 00:06 ./var/volatile/
drwxr-xr-x root/root 0 2011-10-13 00:06 ./var/volatile/log/
drwxr-xr-x root/root 0 2011-10-13 00:06 ./var/volatile/log/ConsoleKit/
drwxr-xr-x root/root 0 2011-10-13 00:06 ./var/volatile/run/
drwxr-xr-x root/root 0 2011-10-13 00:06 ./var/volatile/run/ConsoleKit/
lrwxrwxrwx root/root 0 2011-10-13 00:06 ./var/run - volatile/run
samba_3.5.6-r0_armv7a.ipk
drwxr-xr-x root/root 0 2011-10-13 00:18 ./etc/default/volatiles/
- -rw-r--r-- root/root89 2011-10-13 00:17
./etc/default/volatiles/volatiles.03_samba
lrwxrwxrwx root/root 0 2011-10-13 00:18 ./var/log - volatile/log
lrwxrwxrwx root/root 0 2011-10-13 00:18 ./var/lock - volatile/lock
drwxr-xr-x root/root 0 2011-10-13
[oe] Can't build libcgroup
Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION= 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include-O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory | compilation terminated. | make[2]: *** [libcg_ba.o] Error 1 | make[2]: *** Waiting for unfinished jobs | make[2]: Leaving directory `/home/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/libcgroup-0.37.1-r0/libcgroup-0.37.1/tests' Full compile log at http://www.mlbassoc.com/oe/libcgroup-log.do_compile -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can't build libcgroup
On Oct 13, 2011, at 8:39 AM, Gary Thomas g...@mlbassoc.com wrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION= 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include-O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory | compilation terminated. | make[2]: *** [libcg_ba.o] Error 1 | make[2]: *** Waiting for unfinished jobs | make[2]: Leaving directory `/home/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/libcgroup-0.37.1-r0/libcgroup-0.37.1/tests' Full compile log at http://www.mlbassoc.com/oe/libcgroup-log.do_compile I have the same issue on a 64-bit Ubuntu machine. -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can't build libcgroup
On 2011-10-13 08:16, Kridner, Jason wrote: On Oct 13, 2011, at 8:39 AM, Gary Thomasg...@mlbassoc.com wrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION= 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include-O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory | compilation terminated. | make[2]: *** [libcg_ba.o] Error 1 | make[2]: *** Waiting for unfinished jobs | make[2]: Leaving directory `/home/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/libcgroup-0.37.1-r0/libcgroup-0.37.1/tests' Full compile log at http://www.mlbassoc.com/oe/libcgroup-log.do_compile I have the same issue on a 64-bit Ubuntu machine. Mine is 32 bit Fedora 13. The problem seems to be that G++ 4.5.4 is misconfigured. Running it by hand: [gthomas@titan tests]$ PATH=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi:$PATH arm-angstrom-linux-gnueabi-g++ -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include-O2 -pipe -g -feliminate-unused-debug-types -fpermissive -fvisibility-inlines-hidden -fvisibility-inlines-hidden -c -o libcg_ba.o libcg_ba.cpp -v Using built-in specs. COLLECT_GCC=arm-angstrom-linux-gnueabi-g++ COLLECT_LTO_WRAPPER=/home/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi/../../libexec/armv7a-angstrom-linux-gnueabi/gcc/arm-angstrom-linux-gnueabi/4.5.4/lto-wrapper Target: arm-angstrom-linux-gnueabi Configured with: /local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work-shared/gcc-4.5-r43+svnr178923/gcc-4_5-branch/configure --build=i686-linux --host=i686-linux --target=arm-angstrom-linux-gnueabi --prefix=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr --exec_prefix=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr --bindir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi --sbindir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi --libexecdir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/libexec/armv7a-angstrom-linux-gnueabi --datadir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/share --sysconfdir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/etc --sharedstatedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/com --localstatedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/var --libdir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/lib/armv7a-angstrom-linux-gnueabi --includedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/include --oldincludedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/include --infodir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/share/info --mandir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/share/man --disable-silent-rules --disable-dependency-tracking --with-libtool-sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux --with-gnu-ld --enable-shared --enable-languages=c,c++ --enable-threads=posix --disable-multilib --enable-c99 --enable-long-long --enable-symvers=gnu --enable-libstdcxx-pch --program-prefix=arm-angstrom-linux-gnueabi- --enable-target-optspace --enable-lto --enable-libssp --disable-bootstrap --disable-libgomp --disable-libmudflap --enable-cheaders=c_global --with-local-prefix=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr --with-gxx-include-dir=/usr/include/c++
[oe] [2011.03-maintenance] using sdk as external toolchain
I've built an sdk with oe on the 2011.03-maintenance branch, and I am now trying to set up a local.conf to use the sdk as an external toolchain and I get problems building gtk+-native. any ideas on where I should start debugging this? ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Patches to add support for TI Linux GraphicsSDK release04.04.00.02
Ping ? Hello, This depends on 2.6.37 kernel. http://processors.wiki.ti.com/index.php/RN_4_04_00_02#Kernel.28Linux_PS P.29_versions_used_for_validation which OpenEmbedded (2011.03-maintenance) kernel recipe builds this kernel ? Regards Wolfgang ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Wiki write access disabled?
On Wed, Oct 12, 2011 at 12:38:01PM +0100, Graeme Gregory wrote: Did some experiments with FM on IRC, seems you need the approved flag to be sat to edit wiki now. I don't know what the procedure is to set this flag. I have set it for eFfeM now. I don't want to go ahead and add it for other users without a nod from someone who knows more about the wiki than me. So, how do we go about this limitation? Do we enable write access on a case by case basis? Right now I believe there is only a handful of people allowed to edit Wiki pages... -- Denys I also note the virtual hosting of wiki.openembedded.org/.net is not quite working. You can't log in to .org and all pages seem to be missing on .net domain. Graeme On 12/10/11 08:31, Ulf Samuelsson wrote: Noticed that the wiki seems to be wrong on the 2011.03 release. http://www.openembedded.org/wiki/Release-2011.03 The page tells you to: git checkout release-2011.03 or git checkout -b release-2011.03 origin/release-2011.03 I tried, and that failed. $ git checkout -b ulf/release-2011.03-2011-10-12 origin/release-2011.03 and got the error message. fatal: git checkout: updating paths is incompatible with switching branches. Did you intend to checkout 'origin/release-2011.03' which can not be resolved as commit? $ git remote show origin did not show any release-2011.03, but there is a 2011.03-maintenance which I guess is what you want. Tried to change the http://www.openembedded.org/wiki/Release-2011.03; wiki page to reflect this, but that was not possible, since I did not have write access any longer. Has the rules changed, or is this a mistake in configuration. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Wiki write access disabled?
On 13/10/11 18:06, Denys Dmytriyenko wrote: On Wed, Oct 12, 2011 at 12:38:01PM +0100, Graeme Gregory wrote: Did some experiments with FM on IRC, seems you need the approved flag to be sat to edit wiki now. I don't know what the procedure is to set this flag. I have set it for eFfeM now. I don't want to go ahead and add it for other users without a nod from someone who knows more about the wiki than me. So, how do we go about this limitation? Do we enable write access on a case by case basis? Right now I believe there is only a handful of people allowed to edit Wiki pages... I spoke to the Tom and OE members may talk to a wiki admin, pass a turing test and get added to the approved group. List of admins can be got here http://www.openembedded.org/wiki/Special:ActiveUsers Graeme ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [2011.03-maintenance] using sdk as external toolchain
On Thu, Oct 13, 2011 at 11:22:05AM -0400, George C. Huntington, III wrote: I've built an sdk with oe on the 2011.03-maintenance branch, and I am now trying to set up a local.conf to use the sdk as an external toolchain and I get problems building gtk+-native. any ideas on where I should start debugging this? gtk+-native should be built by the host toolchain, not the target one from SDK - are you sure you are setting all the correct build variables properly? Moreover, it's hard to help you debug your issue, if you don't provide details, such as your local.conf and the build logs... -- Denys ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [2011.03-maintenance] using sdk as external toolchain
On Thu, Oct 13, 2011 at 1:04 PM, Denys Dmytriyenko de...@denix.org wrote: On Thu, Oct 13, 2011 at 11:22:05AM -0400, George C. Huntington, III wrote: I've built an sdk with oe on the 2011.03-maintenance branch, and I am now trying to set up a local.conf to use the sdk as an external toolchain and I get problems building gtk+-native. any ideas on where I should start debugging this? gtk+-native should be built by the host toolchain, not the target one from SDK - are you sure you are setting all the correct build variables properly? I think I am setting the build variables properly, but I'm not quite sure where the correct place to look would be. I was hoping the manual or the wiki would have a this is how you build an SDK and this is how you use the SDK you just built, as an external toolchain I think I get how to build an SDK with the meta-sdk recipe, the other part is less clear. you can talk to me on irc, I use gchiii as my nickname there. Moreover, it's hard to help you debug your issue, if you don't provide details, such as your local.conf and the build logs... -- Denys ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Patches to add support for TI Linux GraphicsSDK release04.04.00.02
Hi, The graphics SDK has been validated with 2.6.32 kernel in OE angstrom environment. The graphics SDK is also validated in standalone environment as well. In standalone validation it has been validated with 2.6.37 kernel as mentioned in the release notes. Thanks, Prathap. -Original Message- From: Hauser, Wolfgang (external) [mailto:wolfgang.hauser.exter...@cassidian.com] Sent: Thursday, October 13, 2011 9:12 PM To: openembedded-devel@lists.openembedded.org Subject: AW: [oe] Patches to add support for TI Linux GraphicsSDK release04.04.00.02 Ping ? Hello, This depends on 2.6.37 kernel. http://processors.wiki.ti.com/index.php/RN_4_04_00_02#Kernel.28Linux_PS P.29_versions_used_for_validation which OpenEmbedded (2011.03-maintenance) kernel recipe builds this kernel ? Regards Wolfgang ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can't build libcgroup
On Thu, Oct 13, 2011 at 7:28 AM, Gary Thomas g...@mlbassoc.com wrote: On 2011-10-13 08:16, Kridner, Jason wrote: On Oct 13, 2011, at 8:39 AM, Gary Thomasg...@mlbassoc.com wrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION = 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO = angstrom DISTRO_VERSION = v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU = vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include -O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory Does this happen with lastest angstrom on oe-core ? or classic oe.dev I am unable to reproduce it on my end | compilation terminated. | make[2]: *** [libcg_ba.o] Error 1 | make[2]: *** Waiting for unfinished jobs | make[2]: Leaving directory `/home/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/libcgroup-0.37.1-r0/libcgroup-0.37.1/tests' Full compile log at http://www.mlbassoc.com/oe/libcgroup-log.do_compile I have the same issue on a 64-bit Ubuntu machine. Mine is 32 bit Fedora 13. The problem seems to be that G++ 4.5.4 is misconfigured. Running it by hand: [gthomas@titan tests]$ PATH=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi:$PATH arm-angstrom-linux-gnueabi-g++ -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include -O2 -pipe -g -feliminate-unused-debug-types -fpermissive -fvisibility-inlines-hidden -fvisibility-inlines-hidden -c -o libcg_ba.o libcg_ba.cpp -v Using built-in specs. COLLECT_GCC=arm-angstrom-linux-gnueabi-g++ COLLECT_LTO_WRAPPER=/home/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi/../../libexec/armv7a-angstrom-linux-gnueabi/gcc/arm-angstrom-linux-gnueabi/4.5.4/lto-wrapper Target: arm-angstrom-linux-gnueabi Configured with: /local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work-shared/gcc-4.5-r43+svnr178923/gcc-4_5-branch/configure --build=i686-linux --host=i686-linux --target=arm-angstrom-linux-gnueabi --prefix=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr --exec_prefix=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr --bindir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi --sbindir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi --libexecdir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/libexec/armv7a-angstrom-linux-gnueabi --datadir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/share --sysconfdir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/etc --sharedstatedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/com --localstatedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/var --libdir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/lib/armv7a-angstrom-linux-gnueabi --includedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/include --oldincludedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/include --infodir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/share/info --mandir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/share/man --disable-silent-rules --disable-dependency-tracking --with-libtool-sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux --with-gnu-ld --enable-shared --enable-languages=c,c++ --enable-threads=posix --disable-multilib --enable-c99 --enable-long-long --enable-symvers=gnu --enable-libstdcxx-pch --program-prefix=arm-angstrom-linux-gnueabi- --enable-target-optspace --enable-lto --enable-libssp --disable-bootstrap --disable-libgomp --disable-libmudflap
Re: [oe] Can't build libcgroup
On 2011-10-13 12:48, Khem Raj wrote: On Thu, Oct 13, 2011 at 7:28 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 08:16, Kridner, Jason wrote: On Oct 13, 2011, at 8:39 AM, Gary Thomasg...@mlbassoc.comwrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION= 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include-O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory Does this happen with lastest angstrom on oe-core ? or classic oe.dev I am unable to reproduce it on my end Latest angstrom with layers as above. | compilation terminated. | make[2]: *** [libcg_ba.o] Error 1 | make[2]: *** Waiting for unfinished jobs | make[2]: Leaving directory `/home/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/libcgroup-0.37.1-r0/libcgroup-0.37.1/tests' Full compile log at http://www.mlbassoc.com/oe/libcgroup-log.do_compile I have the same issue on a 64-bit Ubuntu machine. Mine is 32 bit Fedora 13. The problem seems to be that G++ 4.5.4 is misconfigured. Running it by hand: [gthomas@titan tests]$ PATH=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi:$PATH arm-angstrom-linux-gnueabi-g++ -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include-O2 -pipe -g -feliminate-unused-debug-types -fpermissive -fvisibility-inlines-hidden -fvisibility-inlines-hidden -c -o libcg_ba.o libcg_ba.cpp -v Using built-in specs. COLLECT_GCC=arm-angstrom-linux-gnueabi-g++ COLLECT_LTO_WRAPPER=/home/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi/../../libexec/armv7a-angstrom-linux-gnueabi/gcc/arm-angstrom-linux-gnueabi/4.5.4/lto-wrapper Target: arm-angstrom-linux-gnueabi Configured with: /local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work-shared/gcc-4.5-r43+svnr178923/gcc-4_5-branch/configure --build=i686-linux --host=i686-linux --target=arm-angstrom-linux-gnueabi --prefix=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr --exec_prefix=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr --bindir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi --sbindir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi --libexecdir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/libexec/armv7a-angstrom-linux-gnueabi --datadir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/share --sysconfdir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/etc --sharedstatedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/com --localstatedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/var --libdir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/lib/armv7a-angstrom-linux-gnueabi --includedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/include --oldincludedir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/include --infodir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/share/info --mandir=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/share/man --disable-silent-rules --disable-dependency-tracking --with-libtool-sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux --with-gnu-ld --enable-shared --enable-languages=c,c++ --enable-threads=posix --disable-multilib --enable-c99 --enable-long-long --enable-symvers=gnu --enable-libstdcxx-pch --program-prefix=arm-angstrom-linux-gnueabi- --enable-target-optspace --enable-lto --enable-libssp --disable-bootstrap --disable-libgomp
[oe] [meta-oe][PATCH] ltp-ddt: import initial version 0.0.4 plus fixes
From: Denys Dmytriyenko de...@ti.com
Imported from Arago, adapted for meta-openembedded
Signed-off-by: Denys Dmytriyenko de...@ti.com
---
meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_0.0.4.bb | 63 +
1 files changed, 63 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_0.0.4.bb
diff --git a/meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_0.0.4.bb
b/meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_0.0.4.bb
new file mode 100644
index 000..4b8ff98
--- /dev/null
+++ b/meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_0.0.4.bb
@@ -0,0 +1,63 @@
+DESCRIPTION = Embedded Linux Device Driver Tests based on Linux Test Project
+HOMEPAGE = http://arago-project.org/git/projects/test-automation/ltp-ddt.git;
+SECTION = console/utils
+LICENSE = GPLv2
+LIC_FILES_CHKSUM = file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3
+PR = r1
+
+PROVIDES += ltp
+DEPENDS += zip-native virtual/kernel alsa-lib
+
+inherit autotools
+
+PACKAGE_ARCH = ${MACHINE_ARCH}
+
+SRCREV = 5fba3d42f126ce1fb7d0412d729b753ee5a4
+BRANCH ?= master
+
+SRC_URI =
git://arago-project.org/git/projects/test-automation/ltp-ddt.git;protocol=git;branch=${BRANCH}
+
+S = ${WORKDIR}/git
+
+LTPROOT = /opt/ltp
+
+EXTRA_OEMAKE_append = \
+ prefix=${LTPROOT} \
+ CROSS_COMPILE=${HOST_PREFIX} \
+ SKIP_IDCHECK=1 \
+ KERNEL_INC=${STAGING_KERNEL_DIR}/include \
+ KERNEL_USR_INC=${STAGING_INCDIR} \
+ ALSA_INCPATH=${STAGING_INCDIR} \
+ ALSA_LIBPATH=${STAGING_LIBDIR} \
+ PLATFORM=${MACHINE} \
+
+
+TARGET_CC_ARCH += ${LDFLAGS}
+
+FILES_${PN}-dbg += \
+ ${LTPROOT}/.debug \
+ ${LTPROOT}/bin/.debug \
+ ${LTPROOT}/runtest/.debug \
+ ${LTPROOT}/testcases/bin/.debug \
+ ${LTPROOT}/testcases/bin/*/bin/.debug \
+ ${LTPROOT}/testcases/bin/*/test/.debug \
+ ${LTPROOT}/testcases/bin/ddt/.debug \
+ ${LTPROOT}/testcases/bin/ddt/*/bin/.debug \
+ ${LTPROOT}/testcases/bin/ddt/*/test/.debug \
+
+
+FILES_${PN} += ${LTPROOT}/*
+
+do_configure() {
+ cp ${S}/include/config.h.default ${S}/include/config.h
+ cp ${S}/include/mk/config.mk.default ${S}/include/mk/config.mk
+ cp ${S}/include/mk/features.mk.default ${S}/include/mk/features.mk
+ echo ${TAG} ${S}/ChangeLog
+}
+
+do_install() {
+ oe_runmake DESTDIR=${D} install
+ install -d ${D}${datadir}
+ cp -a ${D}${LTPROOT}/share/* ${D}${datadir}
+ rm -rf ${D}${LTPROOT}/share/
+}
--
1.7.0.4
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [2011.03-maintenance] using sdk as external toolchain
I think my problem was caused by the
PATH_prepend = ${TOOLCHAIN_PATH}/bin:
it seems to catch the pkg-config from the TOOLCHAIN_PATH, instead of the one
in the sysroots/x86_64-linux/usr/bin
when I change to PATH_append = :${TOOLCHAIN_PATH}/bin
it seems to work.
I will wipe out my tmp dir and try again to be sure.
On Thu, Oct 13, 2011 at 2:21 PM, George C. Huntington, III
george.huntington...@gmail.com wrote:
On Thu, Oct 13, 2011 at 1:04 PM, Denys Dmytriyenko de...@denix.orgwrote:
On Thu, Oct 13, 2011 at 11:22:05AM -0400, George C. Huntington, III wrote:
I've built an sdk with oe on the 2011.03-maintenance branch, and I am
now
trying to set up a local.conf to use the sdk as an external toolchain
and I
get problems building gtk+-native. any ideas on where I should start
debugging this?
gtk+-native should be built by the host toolchain, not the target one from
SDK - are you sure you are setting all the correct build variables
properly?
I think I am setting the build variables properly, but I'm not quite sure
where the correct place to look would be.
I was hoping the manual or the wiki would have a this is how you build an
SDK and this is how you use the SDK you just built, as an external
toolchain
I think I get how to build an SDK with the meta-sdk recipe, the other part
is less clear.
you can talk to me on irc, I use gchiii as my nickname there.
Moreover, it's hard to help you debug your issue, if you don't provide
details, such as your local.conf and the build logs...
--
Denys
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can't build libcgroup
On Thu, Oct 13, 2011 at 11:57 AM, Gary Thomas g...@mlbassoc.com wrote: On 2011-10-13 12:48, Khem Raj wrote: On Thu, Oct 13, 2011 at 7:28 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 08:16, Kridner, Jason wrote: On Oct 13, 2011, at 8:39 AM, Gary Thomasg...@mlbassoc.com wrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION = 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO = angstrom DISTRO_VERSION = v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU = vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include -O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory Does this happen with lastest angstrom on oe-core ? or classic oe.dev I am unable to reproduce it on my end Latest angstrom with layers as above. strange, I have it working well for qemuarm and I cant imagine how C++ headers could be broken for beagle ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can't build libcgroup
On 2011-10-13 14:33, Khem Raj wrote: On Thu, Oct 13, 2011 at 11:57 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 12:48, Khem Raj wrote: On Thu, Oct 13, 2011 at 7:28 AM, Gary Thomasg...@mlbassoc.comwrote: On 2011-10-13 08:16, Kridner, Jason wrote: On Oct 13, 2011, at 8:39 AM, Gary Thomasg...@mlbassoc.com wrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION= 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include-O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory Does this happen with lastest angstrom on oe-core ? or classic oe.dev I am unable to reproduce it on my end Latest angstrom with layers as above. strange, I have it working well for qemuarm and I cant imagine how C++ headers could be broken for beagle Maybe you could try it using the Angstrom tools? Here's the [documented] sequence I used: % MACHINE=beagleboard ./oebb.sh config beagleboard ... adjust conf/site.conf for my local DL_DIR ... adjust conf/local.conf to include MACHINE=beagleboard, set parallel build flags, etc ... removed all meta-intel repos from conf/bblayers.conf (to avoid xorg-dri issues) % . ~/.oe/environment-oecore % bitbake systemd-image -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can't build libcgroup
On Thu, Oct 13, 2011 at 1:42 PM, Gary Thomas g...@mlbassoc.com wrote: On 2011-10-13 14:33, Khem Raj wrote: On Thu, Oct 13, 2011 at 11:57 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 12:48, Khem Raj wrote: On Thu, Oct 13, 2011 at 7:28 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 08:16, Kridner, Jason wrote: On Oct 13, 2011, at 8:39 AM, Gary Thomasg...@mlbassoc.com wrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION = 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO = angstrom DISTRO_VERSION = v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU = vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include -O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory Does this happen with lastest angstrom on oe-core ? or classic oe.dev I am unable to reproduce it on my end Latest angstrom with layers as above. strange, I have it working well for qemuarm and I cant imagine how C++ headers could be broken for beagle Maybe you could try it using the Angstrom tools? Here's the [documented] sequence I used: % MACHINE=beagleboard ./oebb.sh config beagleboard ... adjust conf/site.conf for my local DL_DIR ... adjust conf/local.conf to include MACHINE=beagleboard, set parallel build flags, etc ... removed all meta-intel repos from conf/bblayers.conf (to avoid xorg-dri issues) % . ~/.oe/environment-oecore % bitbake systemd-image needless to say thats what I have done but for qemuarm -- Gary Thomas | Consulting for the MLB Associates | Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can't build libcgroup
On 2011-10-13 14:44, Khem Raj wrote: On Thu, Oct 13, 2011 at 1:42 PM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 14:33, Khem Raj wrote: On Thu, Oct 13, 2011 at 11:57 AM, Gary Thomasg...@mlbassoc.comwrote: On 2011-10-13 12:48, Khem Raj wrote: On Thu, Oct 13, 2011 at 7:28 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 08:16, Kridner, Jason wrote: On Oct 13, 2011, at 8:39 AM, Gary Thomasg...@mlbassoc.com wrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION= 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include-O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory Does this happen with lastest angstrom on oe-core ? or classic oe.dev I am unable to reproduce it on my end Latest angstrom with layers as above. strange, I have it working well for qemuarm and I cant imagine how C++ headers could be broken for beagle Maybe you could try it using the Angstrom tools? Here's the [documented] sequence I used: % MACHINE=beagleboard ./oebb.sh config beagleboard ... adjust conf/site.conf for my local DL_DIR ... adjust conf/local.conf to include MACHINE=beagleboard, set parallel build flags, etc ... removed all meta-intel repos from conf/bblayers.conf (to avoid xorg-dri issues) % . ~/.oe/environment-oecore % bitbake systemd-image needless to say thats what I have done but for qemuarm Just making sure :-) I'll try qemuarm here with the same setup. -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can't build libcgroup
On Thursday, October 13, 2011 10:46:48 PM Gary Thomas wrote: On 2011-10-13 14:44, Khem Raj wrote: On Thu, Oct 13, 2011 at 1:42 PM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 14:33, Khem Raj wrote: On Thu, Oct 13, 2011 at 11:57 AM, Gary Thomasg...@mlbassoc.comwrote: On 2011-10-13 12:48, Khem Raj wrote: On Thu, Oct 13, 2011 at 7:28 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 08:16, Kridner, Jason wrote: On Oct 13, 2011, at 8:39 AM, Gary Thomasg...@mlbassoc.com wrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION= 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include-O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory Does this happen with lastest angstrom on oe-core ? or classic oe.dev I am unable to reproduce it on my end Latest angstrom with layers as above. strange, I have it working well for qemuarm and I cant imagine how C++ headers could be broken for beagle Maybe you could try it using the Angstrom tools? Here's the [documented] sequence I used: % MACHINE=beagleboard ./oebb.sh config beagleboard ... adjust conf/site.conf for my local DL_DIR ... adjust conf/local.conf to include MACHINE=beagleboard, set parallel build flags, etc ... removed all meta-intel repos from conf/bblayers.conf (to avoid xorg-dri issues) % . ~/.oe/environment-oecore % bitbake systemd-image needless to say thats what I have done but for qemuarm Just making sure :-) I'll try qemuarm here with the same setup. Hmm few days ago I had unexplainable effects about iostream [1] which could be cleaned by rebuild (and I swear I have seen same for string before) Some race / parallel install issue? [1] http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/010869.html Andreas ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can't build libcgroup
On 2011-10-13 14:58, Andreas Müller wrote: On Thursday, October 13, 2011 10:46:48 PM Gary Thomas wrote: On 2011-10-13 14:44, Khem Raj wrote: On Thu, Oct 13, 2011 at 1:42 PM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 14:33, Khem Raj wrote: On Thu, Oct 13, 2011 at 11:57 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 12:48, Khem Raj wrote: On Thu, Oct 13, 2011 at 7:28 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 08:16, Kridner, Jason wrote: On Oct 13, 2011, at 8:39 AM, Gary Thomasg...@mlbassoc.com wrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION= 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include-O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory Does this happen with lastest angstrom on oe-core ? or classic oe.dev I am unable to reproduce it on my end Latest angstrom with layers as above. strange, I have it working well for qemuarm and I cant imagine how C++ headers could be broken for beagle Maybe you could try it using the Angstrom tools? Here's the [documented] sequence I used: % MACHINE=beagleboard ./oebb.sh config beagleboard ... adjust conf/site.conf for my local DL_DIR ... adjust conf/local.conf to include MACHINE=beagleboard, set parallel build flags, etc ... removed all meta-intel repos from conf/bblayers.conf (to avoid xorg-dri issues) % . ~/.oe/environment-oecore % bitbake systemd-image needless to say thats what I have done but for qemuarm Just making sure :-) I'll try qemuarm here with the same setup. Hmm few days ago I had unexplainable effects about iostream [1] which could be cleaned by rebuild (and I swear I have seen same for string before) Some race / parallel install issue? [1] http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/010869.html If it fails for me again using qemuarm, I'll try a fresh build where I don't try to run full-out -I normally run with: BB_NUMBER_THREADS = 4 PARALLEL_MAKE = -j 4 on a 4-core machine. -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Creating Rootfs images without packages
On Thu, Oct 13, 2011 at 4:07 AM, mgundes mg...@hotmail.com wrote: I meant eliminating whole packages. look at linux from scratch that might be good starting point for such a thing. Sometimes you think that it should be a better way even if you don't know the way. I am not expert on OE and unfortunately I don't have any proposal. I thought there may be or there should be a way to do but if founders and experts don't agree or say current is the best way to go, then everything is ok. May be later, when I learn OE good enough and if I figure out a way I surely share with OE team :) ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] ltp-ddt: import initial version 0.0.4 plus fixes
On Thu, Oct 13, 2011 at 12:55 PM, Denys Dmytriyenko de...@denix.org wrote:
+
+TARGET_CC_ARCH += ${LDFLAGS}
+
why is this needed ?
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can't build libcgroup
On Thu, Oct 13, 2011 at 5:12 PM, Gary Thomas g...@mlbassoc.com wrote: On 2011-10-13 14:58, Andreas Müller wrote: On Thursday, October 13, 2011 10:46:48 PM Gary Thomas wrote: On 2011-10-13 14:44, Khem Raj wrote: On Thu, Oct 13, 2011 at 1:42 PM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 14:33, Khem Raj wrote: On Thu, Oct 13, 2011 at 11:57 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 12:48, Khem Raj wrote: On Thu, Oct 13, 2011 at 7:28 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 08:16, Kridner, Jason wrote: On Oct 13, 2011, at 8:39 AM, Gary Thomasg...@mlbassoc.com wrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION = 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO = angstrom DISTRO_VERSION = v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU = vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include -O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c | libcg_ba.cpp:18:18: fatal error: string: No such file or directory Does this happen with lastest angstrom on oe-core ? or classic oe.dev I am unable to reproduce it on my end Latest angstrom with layers as above. strange, I have it working well for qemuarm and I cant imagine how C++ headers could be broken for beagle Maybe you could try it using the Angstrom tools? Here's the [documented] sequence I used: % MACHINE=beagleboard ./oebb.sh config beagleboard ... adjust conf/site.conf for my local DL_DIR ... adjust conf/local.conf to include MACHINE=beagleboard, set parallel build flags, etc ... removed all meta-intel repos from conf/bblayers.conf (to avoid xorg-dri issues) % . ~/.oe/environment-oecore % bitbake systemd-image needless to say thats what I have done but for qemuarm Just making sure :-) I'll try qemuarm here with the same setup. Hmm few days ago I had unexplainable effects about iostream [1] which could be cleaned by rebuild (and I swear I have seen same for string before) Some race / parallel install issue? [1] http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/010869.html If it fails for me again using qemuarm, I'll try a fresh build where I don't try to run full-out -I normally run with: BB_NUMBER_THREADS = 4 PARALLEL_MAKE = -j 4 on a 4-core machine. I started over and reduced my BB_NUMBER_THREADS to 2, but left my PARALLEL_MAKE at -j24 and the issue went away. I had it set for 8 threads before when it failed. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Can't build libcgroup
On Thursday, October 13, 2011, Jason Kridner jkrid...@beagleboard.org wrote: On Thu, Oct 13, 2011 at 5:12 PM, Gary Thomas g...@mlbassoc.com wrote: On 2011-10-13 14:58, Andreas Müller wrote: On Thursday, October 13, 2011 10:46:48 PM Gary Thomas wrote: On 2011-10-13 14:44, Khem Raj wrote: On Thu, Oct 13, 2011 at 1:42 PM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 14:33, Khem Raj wrote: On Thu, Oct 13, 2011 at 11:57 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 12:48, Khem Raj wrote: On Thu, Oct 13, 2011 at 7:28 AM, Gary Thomasg...@mlbassoc.com wrote: On 2011-10-13 08:16, Kridner, Jason wrote: On Oct 13, 2011, at 8:39 AM, Gary Thomasg...@mlbassoc.com wrote: Trying to follow the Angstrom instructions directly. OE Build Configuration: BB_VERSION= 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= v2011.10-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:66263650f8548d6b0b5f593ab728f536d5e05a9f meta-oe meta-efl meta-gpe meta-gnome meta-xfce = master:1e5d73ec4f44200104de085838f04e31a49435da meta-ti = master:3530f1025efc3792334b897a4e70c6d5822ef56d meta = master:5ad1ca59dea6d5045f252ed7b786ad193faced64 Fails with this error: | ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 -mthumb-interwork -mno-thumb --sysroot=/local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard -DHAVE_CONFIG_H -I. -I.. -I../include-O2 -pipe -g -feliminate-unused-debug-types -Wall -c walk_test.c I started over and reduced my BB_NUMBER_THREADS to 2, but left my PARALLEL_MAKE at -j24 and the issue went away. I had it set for 8 threads before when it failed. Hmm so is it possible that gcc-runtime was not staged Wish I had such monster machines :) ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel th ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
