ok, i can cross that off my list, thanks. rday

1) "This optional GNOME mobile-based UI, which is intended for devices with resolution but restricted size screens ..." pretty sure there's a word missing before "resolution," no? 2) "OpenSUSE" vs "Op

ok, i'm still getting a fetch error for "sat-solver" when trying to do a fetchall for core-image-sato, and here's the log file: fatal: Not a git repository (or any of the parent directories): .git fat

A couple commands are missing the version number directory level under the /opt/poky toolchain installation directory. Signed-off-by: Robert P. J. Day <rpjday@...> --- i'll let scott take t

"--host-armv5te..." should be "--host=armv5te..." Signed-off-by: Robert P. J. Day <rpjday@...> --- there's a fair amount in the ADT manual (and others) that can be cleaned in terms of prope

i saw that a couple days ago but i figured someone else would pick up on it in short order. rday

related to richard's earlier post about how to exclude packages, shouldn't the initial settings be consistent, then? either a default yocto setup should include commercial licenses, or exclude them (a

this is something i noticed a couple days back -- trying to "bitbake -c fetchall world" failed on the sat-solver package: NOTE: Running task 478 of 1358 (ID: 486, /home/rpjday/yocto/poky.git/meta/reci

with latest poky git pull, did "bitbake -c fetchall world" just for fun and got: NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue ERROR: Multiple .bb files are due to be bu

more pedantry: the documentation Makefile reads: ... The command-line argument VER represents the distro # version of the Yocto Release for which the manuals are being generated. # You must invoke the

in trying to resolve a minor issue this weekend regarding PREMIRRORS, i tried to summarize the current set of yocto-related docs and wound up just a bit confused so i'm hoping someone can clarify the

this is also something i should have asked about earlier -- depending on what component you're interested in, there's a different mailing list: bitbake devel list poky list yocto list and perhaps othe

prepping to give a yocto talk to my local (ottawa) LUG next week, and was reviewing the logic of the setup starting with oe-init-build-env, and noticed in scripts/oe-buildenv-internal a test of the va

that's the point i was raising -- that variable's value is obvious, it's just not described anywhere i noticed. rday

i am particulartly interested in this topic as i have two pandaboards waiting to be yocto-ized. might this be a more appropriate topic for the pandaboard mailing list? rday

i ran into this a few weeks back, and i'm still having this grief. I'm running: $ bitbake -c fetchall core-image-sato and it's perpetually failing trying to fetch the sat-solver package. based on the

never mind, just cleared *everything* out and tried again and it worked. mystery. in any event, there's a minor typo in the sat-solver_git.bb file: HOMEPAGE = "http://en.opensue.org/Portal:Libzypp" ^^

i'm guessing it was exactly that -- a stale tarball i didn't realize i was picking up. since now i can't reproduce so i'm going to forget about it unless it happens again. coming shortly. rday

Fix obvious typoes in .bb files for libzypp and sat-solver packages, and update the HOMEPAGE for sat-solver to refer to the sat-solver home page itself, rather than the libzypp home page. Signed-off-b

possibly off-topic but i'm sitting in a fedora/ARM talk right this minute at FSOSS/linuxfest at york u, and the presenter mentioned that when building fedora for pandaboards, they had to back off from