[meta-ti] Building Yocto for Pandaboard
Robert P. J. Day
rpjday at crashcourse.ca
Mon Mar 5 07:48:29 PST 2012
On Mon, 5 Mar 2012, Christian.Schulenberg at bmw.de wrote:
> No, as I wrote previously, the compiler error I have belongs to the
> source code of the bootloader (seems to be a problem with structure
> aligning). The problem you have is in the kernel.
i know ... my question was why you *weren't* getting that build
error. i'm speculating that when you switched back to gcc 4.5 to
solve the u-boot issue, you might have avoided the perf build error as
well.
i'm trying a gcc 4.5 build right now.
rday
>
> -----Ursprüngliche Nachricht-----
> Von: Robert P. J. Day [mailto:rpjday at crashcourse.ca]
> Gesendet: Montag, 5. März 2012 16:17
> An: Schulenberg Christian, EI-42
> Cc: meta-ti at yoctoproject.org
> Betreff: Re: AW: [meta-ti] Building Yocto for Pandaboard
>
> On Mon, 5 Mar 2012, Christian.Schulenberg at bmw.de wrote:
>
> > Hi,
> >
> > I'm using a Pandaboard Rev A4, so it is in fact an OMAP4430 board.
> >
> > You can change to u-boot bootloader in /meta-ti/conf/machine/omap4430-panda.conf:
> >
> > #EXTRA_IMAGEDEPENDS = "x-load u-boot-sakoman " -> remove or comment this line out
> > EXTRA_IMAGEDEPENDS += "u-boot" -> I used this line, but because omap4430-panda.conf includes omap3.inc, it should be obsolete. Same definition is in there. X-Load can be removed from omap3.inc from my point of view, because it's not necessary.
> >
> > #PREFERRED_PROVIDER_virtual/bootloader = "u-boot-sakoman" -> remove or comment this line out
> > PREFERRED_PROVIDER_virtual/bootloader = "u-boot"
> >
> > Your question about gcc4.7: I haven't used this version yet.
> >
> > I have build core-image-base as well as core-image-basic successfully for Pandaboard. I connect to the board via the serial interface, so I don't need a configured eth0 yet.
> >
> > Thanks for your suggestion about systemd. I will try to pull in system in the next days.
>
> without making any of the above changes (since it doesn't appear it
> would affect what i'm doing), i'm getting a build error that goes back
> many months:
>
> ERROR: Function failed: do_compile_perf (see /home/rpjday/yocto/builds/omap4430_panda/tmp/work/omap4430_panda-poky-linux-gnueabi/linux-omap4-2.6.35.7-r0/temp/log.do_compile_perf.29777 for further information)
> NOTE: make -j 8 -C /home/rpjday/yocto/builds/omap4430_panda/tmp/work/omap4430_panda-poky-linux-gnueabi/linux-omap4-2.6.35.7-r0/git/tools/perf CC=arm-poky-linux-gnueabi-gcc -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/home/rpjday/yocto/builds/omap4430_panda/tmp/sysroots/omap4430-panda LD=arm-poky-linux-gnueabi-ld --sysroot=/home/rpjday/yocto/builds/omap4430_panda/tmp/sysroots/omap4430-panda prefix=/usr NO_NEWT=1 NO_DWARF=1
> make: Entering directory `/home/rpjday/yocto/builds/omap4430_panda/tmp/work/omap4430_panda-poky-linux-gnueabi/linux-omap4-2.6.35.7-r0/git/tools/perf'
> PERF_VERSION = ti.ubuntu.2.6.35.993.3
> make: Leaving directory `/home/rpjday/yocto/builds/omap4430_panda/tmp/work/omap4430_panda-poky-linux-gnueabi/linux-omap4-2.6.35.7-r0/git/tools/perf'
> make: Entering directory `/home/rpjday/yocto/builds/omap4430_panda/tmp/work/omap4430_panda-poky-linux-gnueabi/linux-omap4-2.6.35.7-r0/git/tools/perf'
> GEN common-cmds.h
> * new build flags or prefix
> touch .perf.dev.null
> GEN perf-archive
> 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-sched.o
> bench/sched-pipe.c: In function 'bench_sched_pipe':
> bench/sched-pipe.c:58:6: error: variable 'ret' set but not used [-Werror=unused-but-set-variable]
> cc1: all warnings being treated as errors
>
> make: *** [bench/sched-pipe.o] Error 1
> make: *** Waiting for unfinished jobs....
> CC builtin-buildid-list.o
> builtin-sched.c: In function 'process_sched_event':
> builtin-sched.c:373:12: error: variable 'delta' set but not used [-Werror=unused-but-set-variable]
> builtin-sched.c: In function 'run_one_test':
> builtin-sched.c:564:39: error: variable 'std_dev' set but not used [-Werror=unused-but-set-variable]
> builtin-sched.c: In function 'replay_switch_event':
> builtin-sched.c:801:27: error: variable 'next' set but not used [-Werror=unused-but-set-variable]
> builtin-sched.c: In function 'map_switch_event':
> builtin-sched.c:1406:17: error: variable 'sched_out' set but not used [-Werror=unused-but-set-variable]
> cc1: all warnings being treated as errors
>
> make: *** [builtin-sched.o] Error 1
> rm .perf.dev.null
> make: Leaving directory `/home/rpjday/yocto/builds/omap4430_panda/tmp/work/omap4430_panda-poky-linux-gnueabi/linux-omap4-2.6.35.7-r0/git/tools/perf'
> ERROR: oe_runmake failed
>
>
> i'd thought that had been addressed some time back. did you not see
> that build error? does that mean using a different version of gcc
> would resolve it?
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
>
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
More information about the meta-ti
mailing list