Re: [yocto] build failure on denzil-7.0 n450 part 2

2012-07-08 Thread James Abernathy

On Jul 8, 2012, at 1:46 AM, Tom Zanussi wrote:

 On Sat, 2012-07-07 at 12:08 -0500, Tom Zanussi wrote:
 On Sat, 2012-07-07 at 11:59 -0400, jfabernathy wrote:
 Since I started over on my build from the long thread on this subject, I 
 thought I'd start another thread on the issue.
 
 I took the tarball for poky-denzil-7.0 and extracted it into my home 
 directory.  After cd'ing into poky-denzil-7.0, I extracted the 
 n450-denzil-7.0 tarball.
 
 I setup to run a standard default n450 core-image-sato, only changing 
 the linux-yocto_3.2.bbappend by adding in:
 
 SRCREV_machine_pn-linux-yocto_n450 = 
 9d32bb075e349cc69c7af42b60f6715c5d8c972e
 SRCREV_meta_pn-linux-yocto_n450 ?= 
 ee78519365bdb25287703bbc31c06b193263c654
 
 I still get build errors similar to the ones I got with the git 
 repository cloned poky.  Log file below:
 
 
 NOTE: make -C 
 /build/n450-denzil/tmp/work/n450-poky-linux/linux-yocto-3.2.11+git1+ee78519365bdb25287703bbc31c06b193263c654_1+9d32bb075e349cc69c7af42b60f6715c5d8c972e-r1/linux/tools/perf
  
 CC=i586-poky-linux-gcc  -m32-march=core2 -msse3 -mtune=generic 
 -mfpmath=sse --sysroot=/build/n450-denzil/tmp/sysroots/n450 
 LD=i586-poky-linux-ld --sysroot=/build/n450-denzil/tmp/sysroots/n450   
 prefix=/usr NO_NEWT=1 NO_DWARF=1
 make: Entering directory 
 `/build/n450-denzil/tmp/work/n450-poky-linux/linux-yocto-3.2.11+git1+ee78519365bdb25287703bbc31c06b193263c654_1+9d32bb075e349cc69c7af42b60f6715c5d8c972e-r1/linux/tools/perf'
 Makefile:493: libperl not found, disables Perl scripting support. Please 
 install libperl-dev or perl-devel
 PERF_VERSION = 3.2.11.629.g382eda3
 make: Leaving directory 
 `/build/n450-denzil/tmp/work/n450-poky-linux/linux-yocto-3.2.11+git1+ee78519365bdb25287703bbc31c06b193263c654_1+9d32bb075e349cc69c7af42b60f6715c5d8c972e-r1/linux/tools/perf'
 make: Entering directory 
 `/build/n450-denzil/tmp/work/n450-poky-linux/linux-yocto-3.2.11+git1+ee78519365bdb25287703bbc31c06b193263c654_1+9d32bb075e349cc69c7af42b60f6715c5d8c972e-r1/linux/tools/perf'
 Makefile:493: libperl not found, disables Perl scripting support. Please 
 install libperl-dev or perl-devel
 
 
 Yeah, you're still getting the new kernel commits, though you shouldn't
 be, I'll try the same thing here...
 
 
 I tried the same thing here, poky denzil and n450 denzil and it built
 fine with no changes at all.
 
 Somehow your setup is causing the last SRCREVS to be picked up instead
 of what should be - since n450 specifies no SRCREVs, the default SRCREVs
 from linux-yocto_3.2.bb should be getting picked up, and you should see
 those in the build directory name for the kernel as well:
 
 recipes-kernel/linux/linux-yocto_3.2.bb:SRCREV_meta ?= 
 b14a08f5c7b469a5077c10942f4e1aec171faa9d
 recipes-kernel/linux/linux-yocto_3.2.bb:SRCREV_machine ?= 
 01e948c2bdf7f5ad9f2b30047a8d3493a1a2880a
 
 build/tmp/work/n450-poky-linux/linux-yocto-3.2.11+git1+b14a08f5c7b469a5077c10942f4e1aec171faa9d_1+01e948c2bdf7f5ad9f2b30047a8d3493a1a2880a-r1
 
 Since the default SRCREVs use ?= to assign, the likely problem is that
 you already have them assigned to something else before those.
 
 Tom  
 
Well, that is strange.  Before I started I deleted the /build directory, so 
there are no previous build on the computer. I deleted the common download 
area, so there are no previous downloads.  I started with the BSP tarballs for 
poky denzil and n450 denzil.  

Not sure where it could be getting assigned. I'm using Ubuntu 12.04.

Jim A


 Tom
 
 GEN common-cmds.h
 * new build flags or prefix
 CC perf.o
 CC builtin-annotate.o
 CC builtin-bench.o
 CC bench/sched-messaging.o
 CC bench/sched-pipe.o
 CC bench/mem-memcpy.o
 CC builtin-diff.o
 CC builtin-evlist.o
 CC builtin-help.o
 CC builtin-sched.o
 CC builtin-buildid-list.o
 CC builtin-buildid-cache.o
 CC builtin-list.o
 CC builtin-record.o
 CC builtin-report.o
 CC builtin-stat.o
 CC builtin-timechart.o
 CC builtin-top.o
 CC builtin-script.o
 CC builtin-probe.o
 CC builtin-kmem.o
 CC builtin-lock.o
 CC builtin-kvm.o
 CC builtin-test.o
 CC builtin-inject.o
 CC util/abspath.o
 CC util/alias.o
 CC util/annotate.o
 CC util/build-id.o
 CC util/config.o
 CC util/ctype.o
 CC util/debugfs.o
 CC util/environment.o
 CC util/event.o
 CC util/evlist.o
 CC util/evsel.o
 CC util/exec_cmd.o
 CC util/help.o
 CC util/levenshtein.o
 CC util/parse-options.o
 CC util/parse-events.o
 CC util/path.o
 CC util/rbtree.o
 CC util/bitmap.o
 CC util/hweight.o
 CC util/run-command.o
 CC util/quote.o
 CC util/strbuf.o
 CC util/string.o
 CC util/strlist.o
 CC util/strfilter.o
 CC util/top.o
 CC util/usage.o
 CC util/wrapper.o
 CC util/sigchain.o
 CC util/symbol.o
 CC util/color.o
 CC util/pager.o
 CC util/header.o
 CC util/callchain.o
 CC util/values.o
 CC util/debug.o

[yocto] what's the preferred way of creating images for a classic beagle rev C4?

2012-07-08 Thread Robert P. J. Day

  is it adequate to use the canonical beagleboard support in yocto, or
should i take advantage of the developments in the meta-ti layer?
this is for a training course so i don't need production-level
reliability so much as i want access to as many features as i can get
for educational purposes.  thanks.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] meta-toolchain - python not populated properly in sdk

2012-07-08 Thread Jegan Chandru
Hi,

I have a little trouble while building meta-toolchain for my distro. This
is for arm architecture on 64 bit ubuntu 12.04 machine. I use default
bitbake meta-toolchain to create sdk. It created ok, but when I check for
python, it doesnt include everything from build dir. I tried to execute
some scripts using this sdk, but it fails due to some modules missing like
shutils, optparser etc.. I checked the build dir, its all there but not
populated in sdk. I tried to add those by some methods, one of those being
defining my own meta-toolchain-mydistro, but couldnt get full python to get
populated in sdk. Any help with this will deeply appreciated.  what am i
missing?

JC
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto