someone seeing gcc-cross-initial failures since last oe-core upgrade? | /OE/oe-core/tmp-eglibc/work-shared/gcc-4.8.1-r0/gcc-4.8.1/gcc/builtins.c:843:65: error: 'STACK_SAVEAREA_MODE' was not declared in this scope

lpapp: i am sorry. need to get back to (my) work. i recommend you carefully check how 'sub' git are handled in your CI. if you need to understand what bitbake does with git, check out bitbake/lib/bb/fetcher/git.py.

Hey, is anyone here monitoring the oe-develop mailing list/on the general development team? I made a patch commit, and I _think_ I did it right, but I would love for someone to say "Yup, that looks right" before I try and commit the rest of the recipes I wrote.

rburton, I did actually, bluelightening told me the patch itself looks right, but git send-email gave me some complaints about encoding so I put off actually pushing it to today (And today #git told me the server would decode the headers either way). So I am pretty sure it should be right.

hi when i Define iamge_fstype as cpio.gz, will that be a rootfs? I want to make a system with only a kernel(vmlinuz) file an a gpio.gz file with rootfs and all stuff to boot the hole system in an tmpfs, so i can update the system with a new gpio.gz file while its running, is this possible? What Features i will need ?

lpapp, You should be able to set the WORKDIR variable for that. If I understand your question right, no, you can just require the proper class, instead of using do_compile and make, if all you want to do is 'make'.

rburton, Out of curiosity, why would you suspect USB power management of having to do with this? We plug in a USB thing that gives it power, but only when flashing, other than that we use a regular power input.

I'd like to add Qt4 from meta-oe to my distro each time I build it, and looking at the docs it looks as if IMAGE_INSTALL_append = " <packagename>" is how I'm supposed to do it. I'm uncertain of the syntax though... do I just put "qt4" in <packagename> or do I use the bb package name "qt4-embedded_4.8.3" (bb file is qt4-embedded_4.8.3.bb).

when I build "Angstrom" for instance, one of my recipes allows me to build a tool chain. e.g. it creates a file system with INCLUDE populated with the header files for all the installed software and add the cross-comipler for the target system.

I will totally get meta-sourcery working with multilibs and everything. Any minute now. Surely, this will be the last bug I have to remove before my test builds complete on all the targets I care about.

cfo215: what is your base - is it poky or is it oe-core + some distro? in either case the branch of the base determines what other layers should use. if it's master, then other layers should use master. if it's dylan, then same for other layers

lpapp: I'm trying to switch to yocoto/poky instead of angstrom since it seems better supportd. I added the meta-ti layer and updated my local.conf and bblayers.conf but get an error message when bitbaking. http://pastebin.com/cTAFT9xT

Stygia: if there was no reply, and they weren't merged, more likely someone missed reviewing them at all, or hasn't had time to address them. this is fairly common in open source projects. you can always resend them with [resend] or similar in the subject line, but at times you just have to wait. how long as it been since yours were posted?

I think everything takes time to approve. I think my fairly simple and well-liked "set -e" patches took a couple-few months, due to a combination of various people's vacation schedules, higher priority tasks, and so on.

Due to a humorous miscommunication, it turns out it's the first chapter of last year's revised Betty Crocker. Later we will realize that meta-delicious-cookies was the key to Yocto's long-term commercial success.

At one point, we had a couple of months during which something somewhere in an IT department had decided that *some* outgoing mail to the oe-core list would be silently dropped without bounce messages, but mostly it was fine. Only affected us, I think, but there was a period during which maybe 5-10% of attempts to send patches to the list just sort of evaporated.

I added each recipe, used git commit -s, added a commit message (with a summary on the top line), then used this command: git send-email --to=openembedded-devel@lists.openembedded.org --confirm=always -M -1

i have issues building syslinux for meta-intel's nuc, both on master and dylan. (different error messages, at least some variation) :-(. on dylan, i get: "error: CPU you selected does not support x86-64 instruction set" (The compiler command includes -march=i386)

One thing that occasionally bites people in various ways is that x86 systems will occasionally want a given thing built specifically for x86 or x86_64, but by default we build a compiler that only supports one of those.

If you're specifying -march=i386, and getting an error about x86-64 instruction set, that sort of implies that something generated x86-64 instructions or code, or asked for them. Not sure what, without more context. Assembler error?

unfortunately, i don't have any more context than those pastes. afaict, the only usage of -malign-traps=0 in syslinux seems to be falling back when the build system doesn't think the compiler has support for -falign-traps=0.

blueligtning: yes. I just need to be able to run my home-built qt apps on the beaglebone. I took out the IMA... line and the image built w/o errors. Not sure if Qt got in there yet. Haven't had time to look.

I haven't heard of it before, so I don't know. I'm not sure where in the process this is failing, but I guess the first thing I'd probably do is look through any text associated with this for instances of 0xa1, or whatever that value was. If a description is including that character, maybe edit that.

zenlinux: Hi, can you extend http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html to explicitly say that BSP layer shouldn't change metadata for other MACHINEs (i.e. describe that MACHINE overrides have to be used for each assignment/append and MACHINE subdirectories for files used from SRC_URI)? It's hard to explain this to some people and having link to some well written documentation would help a lot, thanks