* Poky on "standard" PC @ 2011-01-24 12:05 Gary Thomas 2011-01-24 12:39 ` Richard Purdie 0 siblings, 1 reply; 13+ messages in thread From: Gary Thomas @ 2011-01-24 12:05 UTC (permalink / raw) To: Poky I wanted to try Poky on a spare laptop, so I went looking for an appropriate configuration to build. From 'README.hardware' (last updated 2010-12-16), I read: Poky Boot CD (bootcdx86) ======================== The Poky boot CD iso images are designed as a demonstration of the Poky environment and to show the versatile image formats Poky can generate. It will run on Pentium2 or greater PC style computers. The iso image can be burnt to CD and then booted from. When I tried it (it's also listed in the default local.conf), I got this error: Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so. Please set a valid MACHINE in your local.conf There seems to be no machine named 'bootcd*' anywhere :-( What should I be using? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-24 12:05 Poky on "standard" PC Gary Thomas @ 2011-01-24 12:39 ` Richard Purdie 2011-01-24 22:54 ` Darren Hart 0 siblings, 1 reply; 13+ messages in thread From: Richard Purdie @ 2011-01-24 12:39 UTC (permalink / raw) To: Gary Thomas; +Cc: Poky On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: > I wanted to try Poky on a spare laptop, so I went looking > for an appropriate configuration to build. > > From 'README.hardware' (last updated 2010-12-16), I read: > Poky Boot CD (bootcdx86) > ======================== > > The Poky boot CD iso images are designed as a demonstration of the Poky > environment and to show the versatile image formats Poky can generate. It will > run on Pentium2 or greater PC style computers. The iso image can be > burnt to CD and then booted from. > > When I tried it (it's also listed in the default local.conf), > I got this error: > Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so. > Please set a valid MACHINE in your local.conf > > There seems to be no machine named 'bootcd*' anywhere :-( > > What should I be using? bootcdx86 was superceeded by the -live images. I'd suggest using the qemux86 or atom-pc machines and building a -live image, dd that to a usb stick and boot that on the laptop. An iso format image is also generated that can be placed onto a CD. We need to remove the bootcdx86 references as they're out of date. Cheers, Richard ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-24 12:39 ` Richard Purdie @ 2011-01-24 22:54 ` Darren Hart 2011-01-25 12:08 ` Gary Thomas 2011-01-25 22:52 ` Richard Purdie 0 siblings, 2 replies; 13+ messages in thread From: Darren Hart @ 2011-01-24 22:54 UTC (permalink / raw) To: Richard Purdie; +Cc: Poky On 01/24/2011 04:39 AM, Richard Purdie wrote: > On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: >> I wanted to try Poky on a spare laptop, so I went looking >> for an appropriate configuration to build. >> >> From 'README.hardware' (last updated 2010-12-16), I read: >> Poky Boot CD (bootcdx86) >> ======================== >> >> The Poky boot CD iso images are designed as a demonstration of the Poky >> environment and to show the versatile image formats Poky can generate. It will >> run on Pentium2 or greater PC style computers. The iso image can be >> burnt to CD and then booted from. >> >> When I tried it (it's also listed in the default local.conf), >> I got this error: >> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so. >> Please set a valid MACHINE in your local.conf >> >> There seems to be no machine named 'bootcd*' anywhere :-( >> >> What should I be using? > > bootcdx86 was superceeded by the -live images. I'd suggest using the > qemux86 or atom-pc machines and building a -live image, dd that to a usb > stick and boot that on the laptop. An iso format image is also generated > that can be placed onto a CD. It will have to be atom-pc as qemu doesn't provide live images (last I checked, a few weeks back). -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-24 22:54 ` Darren Hart @ 2011-01-25 12:08 ` Gary Thomas 2011-01-25 13:45 ` Bruce Ashfield 2011-01-25 22:52 ` Richard Purdie 1 sibling, 1 reply; 13+ messages in thread From: Gary Thomas @ 2011-01-25 12:08 UTC (permalink / raw) To: Darren Hart; +Cc: Poky [-- Attachment #1: Type: text/plain, Size: 1671 bytes --] On 01/24/2011 03:54 PM, Darren Hart wrote: > On 01/24/2011 04:39 AM, Richard Purdie wrote: >> On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: >>> I wanted to try Poky on a spare laptop, so I went looking >>> for an appropriate configuration to build. >>> >>> From 'README.hardware' (last updated 2010-12-16), I read: >>> Poky Boot CD (bootcdx86) >>> ======================== >>> >>> The Poky boot CD iso images are designed as a demonstration of the Poky >>> environment and to show the versatile image formats Poky can generate. It will >>> run on Pentium2 or greater PC style computers. The iso image can be >>> burnt to CD and then booted from. >>> >>> When I tried it (it's also listed in the default local.conf), >>> I got this error: >>> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so. >>> Please set a valid MACHINE in your local.conf >>> >>> There seems to be no machine named 'bootcd*' anywhere :-( >>> >>> What should I be using? >> >> bootcdx86 was superceeded by the -live images. I'd suggest using the >> qemux86 or atom-pc machines and building a -live image, dd that to a usb >> stick and boot that on the laptop. An iso format image is also generated >> that can be placed onto a CD. > > It will have to be atom-pc as qemu doesn't provide live images (last I checked, a few weeks back). Sadly, this doesn't build :-( Failed in compile_perf, log attached. -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ [-- Attachment #2: log.do_compile_perf --] [-- Type: text/plain, Size: 4216 bytes --] NOTE: make -C /home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git0+b0615811ce38836d1ade230e3bdb1efaaa68471f_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/linux/tools/perf CC=ccache i586-poky-linux-gcc -m32 -march=core2 -msse3 -mtune=generic -mfpmath=sse --sysroot=/home/local/pc_poky/tmp/sysroots/core2-poky-linux LD=i586-poky-linux-ld --sysroot=/home/local/pc_poky/tmp/sysroots/core2-poky-linux prefix=/usr make: Entering directory `/home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git0+b0615811ce38836d1ade230e3bdb1efaaa68471f_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/linux/tools/perf' Makefile:508: No libdw.h found or old libdw.h found, disables dwarf support. Please install elfutils-devel/elfutils-dev Makefile:563: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling PERF_VERSION = 0.0.2.PERF make: Leaving directory `/home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git0+b0615811ce38836d1ade230e3bdb1efaaa68471f_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/linux/tools/perf' make: Entering directory `/home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git0+b0615811ce38836d1ade230e3bdb1efaaa68471f_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/linux/tools/perf' Makefile:508: No libdw.h found or old libdw.h found, disables dwarf support. Please install elfutils-devel/elfutils-dev Makefile:563: No bfd.h/libbfd found, install binutils-dev[el]/zlib-static to gain symbol demangling 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-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-trace.o CC builtin-probe.o CC builtin-kmem.o CC builtin-lock.o CC util/abspath.o CC util/alias.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/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/find_next_bit.o CC util/run-command.o CC util/quote.o CC util/strbuf.o CC util/string.o CC util/strlist.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 CC util/map.o CC util/session.o CC util/thread.o CC util/trace-event-parse.o CC util/trace-event-read.o CC util/trace-event-info.o CC util/trace-event-scripting.o CC util/svghelper.o CC util/sort.o CC util/hist.o CC util/probe-event.o CC util/util.o CC util/cpumap.o CC util/scripting-engines/trace-event-perl.o cc1: warnings being treated as errors cc1: error: include location "/usr/local/include" is unsafe for cross-compilation make: *** [util/scripting-engines/trace-event-perl.o] Error 1 make: Leaving directory `/home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git0+b0615811ce38836d1ade230e3bdb1efaaa68471f_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/linux/tools/perf' FATAL: oe_runmake failed Function 'do_compile_perf' failed (see /home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git0+b0615811ce38836d1ade230e3bdb1efaaa68471f_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/temp/log.do_compile_perf.24377 for further information) ERROR: Function 'do_compile_perf' failed (see /home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git0+b0615811ce38836d1ade230e3bdb1efaaa68471f_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/temp/log.do_compile_perf.24377 for further information) ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-25 12:08 ` Gary Thomas @ 2011-01-25 13:45 ` Bruce Ashfield 2011-01-25 16:37 ` Gary Thomas 0 siblings, 1 reply; 13+ messages in thread From: Bruce Ashfield @ 2011-01-25 13:45 UTC (permalink / raw) To: Gary Thomas; +Cc: Poky On Tue, Jan 25, 2011 at 7:08 AM, Gary Thomas <gary@mlbassoc.com> wrote: > On 01/24/2011 03:54 PM, Darren Hart wrote: >> >> On 01/24/2011 04:39 AM, Richard Purdie wrote: >>> >>> On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: >>>> >>>> I wanted to try Poky on a spare laptop, so I went looking >>>> for an appropriate configuration to build. >>>> >>>> From 'README.hardware' (last updated 2010-12-16), I read: >>>> Poky Boot CD (bootcdx86) >>>> ======================== >>>> >>>> The Poky boot CD iso images are designed as a demonstration of the Poky >>>> environment and to show the versatile image formats Poky can generate. >>>> It will >>>> run on Pentium2 or greater PC style computers. The iso image can be >>>> burnt to CD and then booted from. >>>> >>>> When I tried it (it's also listed in the default local.conf), >>>> I got this error: >>>> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does >>>> so. >>>> Please set a valid MACHINE in your local.conf >>>> >>>> There seems to be no machine named 'bootcd*' anywhere :-( >>>> >>>> What should I be using? >>> >>> bootcdx86 was superceeded by the -live images. I'd suggest using the >>> qemux86 or atom-pc machines and building a -live image, dd that to a usb >>> stick and boot that on the laptop. An iso format image is also generated >>> that can be placed onto a CD. >> >> It will have to be atom-pc as qemu doesn't provide live images (last I >> checked, a few weeks back). > > Sadly, this doesn't build :-( Failed in compile_perf, log attached. Hmm. This one was worked around a while ago via: commit d38ad3271829b2d282c973e69edd265ef52174c8 Author: Tom Zanussi <tom.zanussi@intel.com> Date: Fri Jan 14 16:33:05 2011 -0600 linux-yocto: hard-code NO_LIBPERL/NO_LIBPYTHON ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently. This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL. It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet. This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> :100644 100644 21023da... 7833f65... M meta/recipes-kernel/linux/linux-yocto_git.bb But the issue hadn't been showing up on the -stable .. until now. We can cherry pick this patch and commit to at least temporarily work around it. I would have expected the nightly builds to show this one, since not all supported targets have moved to 2.6.37. Bruce > > -- > ------------------------------------------------------------ > Gary Thomas | Consulting for the > MLB Associates | Embedded world > ------------------------------------------------------------ > > _______________________________________________ > poky mailing list > poky@yoctoproject.org > https://lists.yoctoproject.org/listinfo/poky > > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-25 13:45 ` Bruce Ashfield @ 2011-01-25 16:37 ` Gary Thomas 2011-01-25 16:40 ` Bruce Ashfield 0 siblings, 1 reply; 13+ messages in thread From: Gary Thomas @ 2011-01-25 16:37 UTC (permalink / raw) To: Bruce Ashfield; +Cc: Poky On 01/25/2011 06:45 AM, Bruce Ashfield wrote: > On Tue, Jan 25, 2011 at 7:08 AM, Gary Thomas<gary@mlbassoc.com> wrote: >> On 01/24/2011 03:54 PM, Darren Hart wrote: >>> >>> On 01/24/2011 04:39 AM, Richard Purdie wrote: >>>> >>>> On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: >>>>> >>>>> I wanted to try Poky on a spare laptop, so I went looking >>>>> for an appropriate configuration to build. >>>>> >>>>> From 'README.hardware' (last updated 2010-12-16), I read: >>>>> Poky Boot CD (bootcdx86) >>>>> ======================== >>>>> >>>>> The Poky boot CD iso images are designed as a demonstration of the Poky >>>>> environment and to show the versatile image formats Poky can generate. >>>>> It will >>>>> run on Pentium2 or greater PC style computers. The iso image can be >>>>> burnt to CD and then booted from. >>>>> >>>>> When I tried it (it's also listed in the default local.conf), >>>>> I got this error: >>>>> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does >>>>> so. >>>>> Please set a valid MACHINE in your local.conf >>>>> >>>>> There seems to be no machine named 'bootcd*' anywhere :-( >>>>> >>>>> What should I be using? >>>> >>>> bootcdx86 was superceeded by the -live images. I'd suggest using the >>>> qemux86 or atom-pc machines and building a -live image, dd that to a usb >>>> stick and boot that on the laptop. An iso format image is also generated >>>> that can be placed onto a CD. >>> >>> It will have to be atom-pc as qemu doesn't provide live images (last I >>> checked, a few weeks back). >> >> Sadly, this doesn't build :-( Failed in compile_perf, log attached. > > Hmm. This one was worked around a while ago via: > > commit d38ad3271829b2d282c973e69edd265ef52174c8 > Author: Tom Zanussi<tom.zanussi@intel.com> > Date: Fri Jan 14 16:33:05 2011 -0600 > > linux-yocto: hard-code NO_LIBPERL/NO_LIBPYTHON > > ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and > using it to compile perf, which results in a compilation error that > started appearing just recently. > > This turns the code that makes use of ExtUtils::Embed off and simply > hard-codes NO_LIBPERL. > > It does the same for LIBPYTHON while we're at it, since it probably > suffers from a similar underlying problem and just by chance hasn't > broken anything yet. > > This will be re-enabled after I familiarize myself with the perf > recipe and am able to create a proper fix. > > Signed-off-by: Tom Zanussi<tom.zanussi@intel.com> > > :100644 100644 21023da... 7833f65... M > meta/recipes-kernel/linux/linux-yocto_git.bb > > But the issue hadn't been showing up on the -stable .. until now. We can cherry > pick this patch and commit to at least temporarily work around it. > > I would have expected the nightly builds to show this one, since not all > supported targets have moved to 2.6.37. I just updated to the latest master and started from scratch. It's still happening :-( OE Build Configuration: BB_VERSION = "1.11.0" METADATA_BRANCH = "master" METADATA_REVISION = "beb9166b3adf83c5e864afcb56cf9ea24f55a7c3" TARGET_ARCH = "i586" TARGET_OS = "linux" MACHINE = "atom-pc" DISTRO = "poky" DISTRO_VERSION = "0.9+snapshot-20110125" TARGET_FPU = "" | CC util/scripting-engines/trace-event-perl.o | cc1: warnings being treated as errors | cc1: error: include location "/usr/local/include" is unsafe for cross-compilation | make: *** [util/scripting-engines/trace-event-perl.o] Error 1 | make: Leaving directory `/home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/linux/tools/perf' | FATAL: oe_runmake failed | Function 'do_compile_perf' failed (see /home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/temp/log.do_compile_perf.8191 for further information) | ERROR: Function 'do_compile_perf' failed (see /home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/temp/log.do_compile_perf.8191 for further information) NOTE: package linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1: task do_compile_perf: Failed Maybe it has something to do with my build host (Fedora-13, x86)? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-25 16:37 ` Gary Thomas @ 2011-01-25 16:40 ` Bruce Ashfield 2011-01-25 16:45 ` Gary Thomas 0 siblings, 1 reply; 13+ messages in thread From: Bruce Ashfield @ 2011-01-25 16:40 UTC (permalink / raw) To: Gary Thomas; +Cc: Poky On 11-01-25 11:37 AM, Gary Thomas wrote: > On 01/25/2011 06:45 AM, Bruce Ashfield wrote: >> On Tue, Jan 25, 2011 at 7:08 AM, Gary Thomas<gary@mlbassoc.com> wrote: >>> On 01/24/2011 03:54 PM, Darren Hart wrote: >>>> >>>> On 01/24/2011 04:39 AM, Richard Purdie wrote: >>>>> >>>>> On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: >>>>>> >>>>>> I wanted to try Poky on a spare laptop, so I went looking >>>>>> for an appropriate configuration to build. >>>>>> >>>>>> From 'README.hardware' (last updated 2010-12-16), I read: >>>>>> Poky Boot CD (bootcdx86) >>>>>> ======================== >>>>>> >>>>>> The Poky boot CD iso images are designed as a demonstration of the >>>>>> Poky >>>>>> environment and to show the versatile image formats Poky can >>>>>> generate. >>>>>> It will >>>>>> run on Pentium2 or greater PC style computers. The iso image can be >>>>>> burnt to CD and then booted from. >>>>>> >>>>>> When I tried it (it's also listed in the default local.conf), >>>>>> I got this error: >>>>>> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO >>>>>> that does >>>>>> so. >>>>>> Please set a valid MACHINE in your local.conf >>>>>> >>>>>> There seems to be no machine named 'bootcd*' anywhere :-( >>>>>> >>>>>> What should I be using? >>>>> >>>>> bootcdx86 was superceeded by the -live images. I'd suggest using the >>>>> qemux86 or atom-pc machines and building a -live image, dd that to >>>>> a usb >>>>> stick and boot that on the laptop. An iso format image is also >>>>> generated >>>>> that can be placed onto a CD. >>>> >>>> It will have to be atom-pc as qemu doesn't provide live images (last I >>>> checked, a few weeks back). >>> >>> Sadly, this doesn't build :-( Failed in compile_perf, log attached. >> >> Hmm. This one was worked around a while ago via: >> >> commit d38ad3271829b2d282c973e69edd265ef52174c8 >> Author: Tom Zanussi<tom.zanussi@intel.com> >> Date: Fri Jan 14 16:33:05 2011 -0600 >> >> linux-yocto: hard-code NO_LIBPERL/NO_LIBPYTHON >> >> ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and >> using it to compile perf, which results in a compilation error that >> started appearing just recently. >> >> This turns the code that makes use of ExtUtils::Embed off and simply >> hard-codes NO_LIBPERL. >> >> It does the same for LIBPYTHON while we're at it, since it probably >> suffers from a similar underlying problem and just by chance hasn't >> broken anything yet. >> >> This will be re-enabled after I familiarize myself with the perf >> recipe and am able to create a proper fix. >> >> Signed-off-by: Tom Zanussi<tom.zanussi@intel.com> >> >> :100644 100644 21023da... 7833f65... M >> meta/recipes-kernel/linux/linux-yocto_git.bb >> >> But the issue hadn't been showing up on the -stable .. until now. We >> can cherry >> pick this patch and commit to at least temporarily work around it. >> >> I would have expected the nightly builds to show this one, since not all >> supported targets have moved to 2.6.37. > > I just updated to the latest master and started from scratch. > It's still happening :-( > > OE Build Configuration: > BB_VERSION = "1.11.0" > METADATA_BRANCH = "master" > METADATA_REVISION = "beb9166b3adf83c5e864afcb56cf9ea24f55a7c3" > TARGET_ARCH = "i586" > TARGET_OS = "linux" > MACHINE = "atom-pc" > DISTRO = "poky" > DISTRO_VERSION = "0.9+snapshot-20110125" > TARGET_FPU = "" > > | CC util/scripting-engines/trace-event-perl.o > | cc1: warnings being treated as errors > | cc1: error: include location "/usr/local/include" is unsafe for > cross-compilation > | make: *** [util/scripting-engines/trace-event-perl.o] Error 1 > | make: Leaving directory > `/home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/linux/tools/perf' > > | FATAL: oe_runmake failed > | Function 'do_compile_perf' failed (see > /home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/temp/log.do_compile_perf.8191 > for further information) > | ERROR: Function 'do_compile_perf' failed (see > /home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/temp/log.do_compile_perf.8191 > for further information) > NOTE: package > linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1: > task do_compile_perf: Failed > > Maybe it has something to do with my build host (Fedora-13, x86)? In this case the host is fine. That commit was on the 2.6.37 kernel, and I used your report as a trigger and backported it to 2.6.34. I have a pull request out now, which should fixup the perf compilation issues once merged. Bruce > ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-25 16:40 ` Bruce Ashfield @ 2011-01-25 16:45 ` Gary Thomas 2011-01-25 20:16 ` Saul Wold 0 siblings, 1 reply; 13+ messages in thread From: Gary Thomas @ 2011-01-25 16:45 UTC (permalink / raw) To: Bruce Ashfield; +Cc: Poky On 01/25/2011 09:40 AM, Bruce Ashfield wrote: > On 11-01-25 11:37 AM, Gary Thomas wrote: >> On 01/25/2011 06:45 AM, Bruce Ashfield wrote: >>> On Tue, Jan 25, 2011 at 7:08 AM, Gary Thomas<gary@mlbassoc.com> wrote: >>>> On 01/24/2011 03:54 PM, Darren Hart wrote: >>>>> >>>>> On 01/24/2011 04:39 AM, Richard Purdie wrote: >>>>>> >>>>>> On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: >>>>>>> >>>>>>> I wanted to try Poky on a spare laptop, so I went looking >>>>>>> for an appropriate configuration to build. >>>>>>> >>>>>>> From 'README.hardware' (last updated 2010-12-16), I read: >>>>>>> Poky Boot CD (bootcdx86) >>>>>>> ======================== >>>>>>> >>>>>>> The Poky boot CD iso images are designed as a demonstration of the >>>>>>> Poky >>>>>>> environment and to show the versatile image formats Poky can >>>>>>> generate. >>>>>>> It will >>>>>>> run on Pentium2 or greater PC style computers. The iso image can be >>>>>>> burnt to CD and then booted from. >>>>>>> >>>>>>> When I tried it (it's also listed in the default local.conf), >>>>>>> I got this error: >>>>>>> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO >>>>>>> that does >>>>>>> so. >>>>>>> Please set a valid MACHINE in your local.conf >>>>>>> >>>>>>> There seems to be no machine named 'bootcd*' anywhere :-( >>>>>>> >>>>>>> What should I be using? >>>>>> >>>>>> bootcdx86 was superceeded by the -live images. I'd suggest using the >>>>>> qemux86 or atom-pc machines and building a -live image, dd that to >>>>>> a usb >>>>>> stick and boot that on the laptop. An iso format image is also >>>>>> generated >>>>>> that can be placed onto a CD. >>>>> >>>>> It will have to be atom-pc as qemu doesn't provide live images (last I >>>>> checked, a few weeks back). >>>> >>>> Sadly, this doesn't build :-( Failed in compile_perf, log attached. >>> >>> Hmm. This one was worked around a while ago via: >>> >>> commit d38ad3271829b2d282c973e69edd265ef52174c8 >>> Author: Tom Zanussi<tom.zanussi@intel.com> >>> Date: Fri Jan 14 16:33:05 2011 -0600 >>> >>> linux-yocto: hard-code NO_LIBPERL/NO_LIBPYTHON >>> >>> ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and >>> using it to compile perf, which results in a compilation error that >>> started appearing just recently. >>> >>> This turns the code that makes use of ExtUtils::Embed off and simply >>> hard-codes NO_LIBPERL. >>> >>> It does the same for LIBPYTHON while we're at it, since it probably >>> suffers from a similar underlying problem and just by chance hasn't >>> broken anything yet. >>> >>> This will be re-enabled after I familiarize myself with the perf >>> recipe and am able to create a proper fix. >>> >>> Signed-off-by: Tom Zanussi<tom.zanussi@intel.com> >>> >>> :100644 100644 21023da... 7833f65... M >>> meta/recipes-kernel/linux/linux-yocto_git.bb >>> >>> But the issue hadn't been showing up on the -stable .. until now. We >>> can cherry >>> pick this patch and commit to at least temporarily work around it. >>> >>> I would have expected the nightly builds to show this one, since not all >>> supported targets have moved to 2.6.37. >> >> I just updated to the latest master and started from scratch. >> It's still happening :-( >> >> OE Build Configuration: >> BB_VERSION = "1.11.0" >> METADATA_BRANCH = "master" >> METADATA_REVISION = "beb9166b3adf83c5e864afcb56cf9ea24f55a7c3" >> TARGET_ARCH = "i586" >> TARGET_OS = "linux" >> MACHINE = "atom-pc" >> DISTRO = "poky" >> DISTRO_VERSION = "0.9+snapshot-20110125" >> TARGET_FPU = "" >> >> | CC util/scripting-engines/trace-event-perl.o >> | cc1: warnings being treated as errors >> | cc1: error: include location "/usr/local/include" is unsafe for >> cross-compilation >> | make: *** [util/scripting-engines/trace-event-perl.o] Error 1 >> | make: Leaving directory >> `/home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/linux/tools/perf' >> >> >> | FATAL: oe_runmake failed >> | Function 'do_compile_perf' failed (see >> /home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/temp/log.do_compile_perf.8191 >> >> for further information) >> | ERROR: Function 'do_compile_perf' failed (see >> /home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/temp/log.do_compile_perf.8191 >> >> for further information) >> NOTE: package >> linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1: >> task do_compile_perf: Failed >> >> Maybe it has something to do with my build host (Fedora-13, x86)? > > In this case the host is fine. That commit was on the > 2.6.37 kernel, and I used your report as a trigger and > backported it to 2.6.34. I have a pull request out now, > which should fixup the perf compilation issues once > merged. Thanks, I'll try it with your patch. -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-25 16:45 ` Gary Thomas @ 2011-01-25 20:16 ` Saul Wold 0 siblings, 0 replies; 13+ messages in thread From: Saul Wold @ 2011-01-25 20:16 UTC (permalink / raw) To: Gary Thomas; +Cc: Poky On 01/25/2011 08:45 AM, Gary Thomas wrote: > On 01/25/2011 09:40 AM, Bruce Ashfield wrote: >> On 11-01-25 11:37 AM, Gary Thomas wrote: >>> On 01/25/2011 06:45 AM, Bruce Ashfield wrote: >>>> On Tue, Jan 25, 2011 at 7:08 AM, Gary Thomas<gary@mlbassoc.com> wrote: >>>>> On 01/24/2011 03:54 PM, Darren Hart wrote: >>>>>> >>>>>> On 01/24/2011 04:39 AM, Richard Purdie wrote: >>>>>>> >>>>>>> On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: >>>>>>>> >>>>>>>> I wanted to try Poky on a spare laptop, so I went looking >>>>>>>> for an appropriate configuration to build. >>>>>>>> >>>>>>>> From 'README.hardware' (last updated 2010-12-16), I read: >>>>>>>> Poky Boot CD (bootcdx86) >>>>>>>> ======================== >>>>>>>> >>>>>>>> The Poky boot CD iso images are designed as a demonstration of the >>>>>>>> Poky >>>>>>>> environment and to show the versatile image formats Poky can >>>>>>>> generate. >>>>>>>> It will >>>>>>>> run on Pentium2 or greater PC style computers. The iso image can be >>>>>>>> burnt to CD and then booted from. >>>>>>>> >>>>>>>> When I tried it (it's also listed in the default local.conf), >>>>>>>> I got this error: >>>>>>>> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO >>>>>>>> that does >>>>>>>> so. >>>>>>>> Please set a valid MACHINE in your local.conf >>>>>>>> >>>>>>>> There seems to be no machine named 'bootcd*' anywhere :-( >>>>>>>> >>>>>>>> What should I be using? >>>>>>> >>>>>>> bootcdx86 was superceeded by the -live images. I'd suggest using the >>>>>>> qemux86 or atom-pc machines and building a -live image, dd that to >>>>>>> a usb >>>>>>> stick and boot that on the laptop. An iso format image is also >>>>>>> generated >>>>>>> that can be placed onto a CD. >>>>>> >>>>>> It will have to be atom-pc as qemu doesn't provide live images >>>>>> (last I >>>>>> checked, a few weeks back). >>>>> >>>>> Sadly, this doesn't build :-( Failed in compile_perf, log attached. >>>> >>>> Hmm. This one was worked around a while ago via: >>>> >>>> commit d38ad3271829b2d282c973e69edd265ef52174c8 >>>> Author: Tom Zanussi<tom.zanussi@intel.com> >>>> Date: Fri Jan 14 16:33:05 2011 -0600 >>>> >>>> linux-yocto: hard-code NO_LIBPERL/NO_LIBPYTHON >>>> >>>> ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and >>>> using it to compile perf, which results in a compilation error that >>>> started appearing just recently. >>>> >>>> This turns the code that makes use of ExtUtils::Embed off and simply >>>> hard-codes NO_LIBPERL. >>>> >>>> It does the same for LIBPYTHON while we're at it, since it probably >>>> suffers from a similar underlying problem and just by chance hasn't >>>> broken anything yet. >>>> >>>> This will be re-enabled after I familiarize myself with the perf >>>> recipe and am able to create a proper fix. >>>> >>>> Signed-off-by: Tom Zanussi<tom.zanussi@intel.com> >>>> >>>> :100644 100644 21023da... 7833f65... M >>>> meta/recipes-kernel/linux/linux-yocto_git.bb >>>> >>>> But the issue hadn't been showing up on the -stable .. until now. We >>>> can cherry >>>> pick this patch and commit to at least temporarily work around it. >>>> >>>> I would have expected the nightly builds to show this one, since not >>>> all >>>> supported targets have moved to 2.6.37. >>> >>> I just updated to the latest master and started from scratch. >>> It's still happening :-( >>> >>> OE Build Configuration: >>> BB_VERSION = "1.11.0" >>> METADATA_BRANCH = "master" >>> METADATA_REVISION = "beb9166b3adf83c5e864afcb56cf9ea24f55a7c3" >>> TARGET_ARCH = "i586" >>> TARGET_OS = "linux" >>> MACHINE = "atom-pc" >>> DISTRO = "poky" >>> DISTRO_VERSION = "0.9+snapshot-20110125" >>> TARGET_FPU = "" >>> >>> | CC util/scripting-engines/trace-event-perl.o >>> | cc1: warnings being treated as errors >>> | cc1: error: include location "/usr/local/include" is unsafe for >>> cross-compilation >>> | make: *** [util/scripting-engines/trace-event-perl.o] Error 1 >>> | make: Leaving directory >>> `/home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/linux/tools/perf' >>> >>> >>> >>> | FATAL: oe_runmake failed >>> | Function 'do_compile_perf' failed (see >>> /home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/temp/log.do_compile_perf.8191 >>> >>> >>> for further information) >>> | ERROR: Function 'do_compile_perf' failed (see >>> /home/local/pc_poky/tmp/work/atom-pc-poky-linux/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1/temp/log.do_compile_perf.8191 >>> >>> >>> for further information) >>> NOTE: package >>> linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_0+35521a5a70316785a67aca1de1d39a7b84c49ccf-r1: >>> >>> task do_compile_perf: Failed >>> >>> Maybe it has something to do with my build host (Fedora-13, x86)? >> >> In this case the host is fine. That commit was on the >> 2.6.37 kernel, and I used your report as a trigger and >> backported it to 2.6.34. I have a pull request out now, >> which should fixup the perf compilation issues once >> merged. > > Thanks, I'll try it with your patch. > This has been patched in master now also. Sau! ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-24 22:54 ` Darren Hart 2011-01-25 12:08 ` Gary Thomas @ 2011-01-25 22:52 ` Richard Purdie 2011-01-26 0:30 ` Darren Hart 1 sibling, 1 reply; 13+ messages in thread From: Richard Purdie @ 2011-01-25 22:52 UTC (permalink / raw) To: Darren Hart; +Cc: Poky On Mon, 2011-01-24 at 14:54 -0800, Darren Hart wrote: > On 01/24/2011 04:39 AM, Richard Purdie wrote: > > On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: > >> I wanted to try Poky on a spare laptop, so I went looking > >> for an appropriate configuration to build. > >> > >> From 'README.hardware' (last updated 2010-12-16), I read: > >> Poky Boot CD (bootcdx86) > >> ======================== > >> > >> The Poky boot CD iso images are designed as a demonstration of the Poky > >> environment and to show the versatile image formats Poky can generate. It will > >> run on Pentium2 or greater PC style computers. The iso image can be > >> burnt to CD and then booted from. > >> > >> When I tried it (it's also listed in the default local.conf), > >> I got this error: > >> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so. > >> Please set a valid MACHINE in your local.conf > >> > >> There seems to be no machine named 'bootcd*' anywhere :-( > >> > >> What should I be using? > > > > bootcdx86 was superceeded by the -live images. I'd suggest using the > > qemux86 or atom-pc machines and building a -live image, dd that to a usb > > stick and boot that on the laptop. An iso format image is also generated > > that can be placed onto a CD. > > It will have to be atom-pc as qemu doesn't provide live images (last I > checked, a few weeks back). I don't see why the qemu machine wouldn't work for the live image variants, even if we don't build them by default on the autobuilder? atom-pc is fine though... Cheers, Richard ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-25 22:52 ` Richard Purdie @ 2011-01-26 0:30 ` Darren Hart 2011-01-26 1:37 ` Gary Thomas 0 siblings, 1 reply; 13+ messages in thread From: Darren Hart @ 2011-01-26 0:30 UTC (permalink / raw) To: Richard Purdie; +Cc: Poky On 01/25/2011 02:52 PM, Richard Purdie wrote: > On Mon, 2011-01-24 at 14:54 -0800, Darren Hart wrote: >> On 01/24/2011 04:39 AM, Richard Purdie wrote: >>> On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: >>>> I wanted to try Poky on a spare laptop, so I went looking >>>> for an appropriate configuration to build. >>>> >>>> From 'README.hardware' (last updated 2010-12-16), I read: >>>> Poky Boot CD (bootcdx86) >>>> ======================== >>>> >>>> The Poky boot CD iso images are designed as a demonstration of the Poky >>>> environment and to show the versatile image formats Poky can generate. It will >>>> run on Pentium2 or greater PC style computers. The iso image can be >>>> burnt to CD and then booted from. >>>> >>>> When I tried it (it's also listed in the default local.conf), >>>> I got this error: >>>> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so. >>>> Please set a valid MACHINE in your local.conf >>>> >>>> There seems to be no machine named 'bootcd*' anywhere :-( >>>> >>>> What should I be using? >>> >>> bootcdx86 was superceeded by the -live images. I'd suggest using the >>> qemux86 or atom-pc machines and building a -live image, dd that to a usb >>> stick and boot that on the laptop. An iso format image is also generated >>> that can be placed onto a CD. >> >> It will have to be atom-pc as qemu doesn't provide live images (last I >> checked, a few weeks back). > > I don't see why the qemu machine wouldn't work for the live image > variants, even if we don't build them by default on the autobuilder? When I run: $ MACHINE="qemux86" bitbake poky-image-minimal-live it results it: ERROR: '/home/dvhart/data/poky.git/meta/recipes-core/images/poky-image-minimal-live.bb' failed ERROR: Function 'build_boot_bin' failed (see /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 for further information) ERROR: Logfile of failure stored in: /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 Log data follows: | install: cannot stat `/vol/1/dvhart/poky.git/build/tmp/sysroots/qemux86-poky-linux/kernel/bzImage': No such file or directory | Function 'build_boot_bin' failed (see /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 for further information) | ERROR: Function 'build_boot_bin' failed (see /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 for further information) NOTE: package poky-image-minimal-live-1.0-r0: task build_boot_bin: Failed ERROR: Task 9 (/home/dvhart/data/poky.git/meta/recipes-core/images/poky-image-minimal-live.bb, do_bootimg) failed with exit code '1' -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-26 0:30 ` Darren Hart @ 2011-01-26 1:37 ` Gary Thomas 2011-01-26 19:31 ` Darren Hart 0 siblings, 1 reply; 13+ messages in thread From: Gary Thomas @ 2011-01-26 1:37 UTC (permalink / raw) To: Darren Hart; +Cc: Poky On 01/25/2011 05:30 PM, Darren Hart wrote: > On 01/25/2011 02:52 PM, Richard Purdie wrote: >> On Mon, 2011-01-24 at 14:54 -0800, Darren Hart wrote: >>> On 01/24/2011 04:39 AM, Richard Purdie wrote: >>>> On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: >>>>> I wanted to try Poky on a spare laptop, so I went looking >>>>> for an appropriate configuration to build. >>>>> >>>>> From 'README.hardware' (last updated 2010-12-16), I read: >>>>> Poky Boot CD (bootcdx86) >>>>> ======================== >>>>> >>>>> The Poky boot CD iso images are designed as a demonstration of the Poky >>>>> environment and to show the versatile image formats Poky can generate. It will >>>>> run on Pentium2 or greater PC style computers. The iso image can be >>>>> burnt to CD and then booted from. >>>>> >>>>> When I tried it (it's also listed in the default local.conf), >>>>> I got this error: >>>>> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO that does so. >>>>> Please set a valid MACHINE in your local.conf >>>>> >>>>> There seems to be no machine named 'bootcd*' anywhere :-( >>>>> >>>>> What should I be using? >>>> >>>> bootcdx86 was superceeded by the -live images. I'd suggest using the >>>> qemux86 or atom-pc machines and building a -live image, dd that to a usb >>>> stick and boot that on the laptop. An iso format image is also generated >>>> that can be placed onto a CD. >>> >>> It will have to be atom-pc as qemu doesn't provide live images (last I >>> checked, a few weeks back). >> >> I don't see why the qemu machine wouldn't work for the live image >> variants, even if we don't build them by default on the autobuilder? > > When I run: > > $ MACHINE="qemux86" bitbake poky-image-minimal-live > > it results it: > > ERROR: '/home/dvhart/data/poky.git/meta/recipes-core/images/poky-image-minimal-live.bb' failed > ERROR: Function 'build_boot_bin' failed (see /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 for further information) > ERROR: Logfile of failure stored in: /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 > Log data follows: > | install: cannot stat `/vol/1/dvhart/poky.git/build/tmp/sysroots/qemux86-poky-linux/kernel/bzImage': No such file or directory > | Function 'build_boot_bin' failed (see /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 for further information) > | ERROR: Function 'build_boot_bin' failed (see /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 for further information) > NOTE: package poky-image-minimal-live-1.0-r0: task build_boot_bin: Failed > ERROR: Task 9 (/home/dvhart/data/poky.git/meta/recipes-core/images/poky-image-minimal-live.bb, do_bootimg) failed with exit code '1' This worked for me. Are you sure your repo is up to date? I think the fix was in commit bc9d2fbfd4eaad0df5647dd5d07dfb9fcff80ff3 Author: Dongxiao Xu <dongxiao.xu@intel.com> Date: Tue Jan 18 16:17:58 2011 +0800 staging: Use relative path in sysroot-destdir for target recipes -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Poky on "standard" PC 2011-01-26 1:37 ` Gary Thomas @ 2011-01-26 19:31 ` Darren Hart 0 siblings, 0 replies; 13+ messages in thread From: Darren Hart @ 2011-01-26 19:31 UTC (permalink / raw) To: Gary Thomas; +Cc: Poky On 01/25/2011 05:37 PM, Gary Thomas wrote: > On 01/25/2011 05:30 PM, Darren Hart wrote: >> On 01/25/2011 02:52 PM, Richard Purdie wrote: >>> On Mon, 2011-01-24 at 14:54 -0800, Darren Hart wrote: >>>> On 01/24/2011 04:39 AM, Richard Purdie wrote: >>>>> On Mon, 2011-01-24 at 05:05 -0700, Gary Thomas wrote: >>>>>> I wanted to try Poky on a spare laptop, so I went looking >>>>>> for an appropriate configuration to build. >>>>>> >>>>>> From 'README.hardware' (last updated 2010-12-16), I read: >>>>>> Poky Boot CD (bootcdx86) >>>>>> ======================== >>>>>> >>>>>> The Poky boot CD iso images are designed as a demonstration of the >>>>>> Poky >>>>>> environment and to show the versatile image formats Poky can >>>>>> generate. It will >>>>>> run on Pentium2 or greater PC style computers. The iso image can be >>>>>> burnt to CD and then booted from. >>>>>> >>>>>> When I tried it (it's also listed in the default local.conf), >>>>>> I got this error: >>>>>> Please set TARGET_ARCH directly, or choose a MACHINE or DISTRO >>>>>> that does so. >>>>>> Please set a valid MACHINE in your local.conf >>>>>> >>>>>> There seems to be no machine named 'bootcd*' anywhere :-( >>>>>> >>>>>> What should I be using? >>>>> >>>>> bootcdx86 was superceeded by the -live images. I'd suggest using the >>>>> qemux86 or atom-pc machines and building a -live image, dd that to >>>>> a usb >>>>> stick and boot that on the laptop. An iso format image is also >>>>> generated >>>>> that can be placed onto a CD. >>>> >>>> It will have to be atom-pc as qemu doesn't provide live images (last I >>>> checked, a few weeks back). >>> >>> I don't see why the qemu machine wouldn't work for the live image >>> variants, even if we don't build them by default on the autobuilder? >> >> When I run: >> >> $ MACHINE="qemux86" bitbake poky-image-minimal-live >> >> it results it: >> >> ERROR: >> '/home/dvhart/data/poky.git/meta/recipes-core/images/poky-image-minimal-live.bb' >> failed >> ERROR: Function 'build_boot_bin' failed (see >> /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 >> for further information) >> ERROR: Logfile of failure stored in: >> /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 >> >> Log data follows: >> | install: cannot stat >> `/vol/1/dvhart/poky.git/build/tmp/sysroots/qemux86-poky-linux/kernel/bzImage': >> No such file or directory >> | Function 'build_boot_bin' failed (see >> /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 >> for further information) >> | ERROR: Function 'build_boot_bin' failed (see >> /vol/1/dvhart/poky.git/build/tmp/work/i586-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.18423 >> for further information) >> NOTE: package poky-image-minimal-live-1.0-r0: task build_boot_bin: Failed >> ERROR: Task 9 >> (/home/dvhart/data/poky.git/meta/recipes-core/images/poky-image-minimal-live.bb, >> do_bootimg) failed with exit code '1' > > This worked for me. Are you sure your repo is up to date? > I think the fix was in > commit bc9d2fbfd4eaad0df5647dd5d07dfb9fcff80ff3 > Author: Dongxiao Xu <dongxiao.xu@intel.com> > Date: Tue Jan 18 16:17:58 2011 +0800 I did have the above patch, but refreshing again to master's HEAD and rebuilding seems to have worked. I also purged tmp and sstate, perhaps I had something stuck in there. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2011-01-26 19:31 UTC | newest] Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2011-01-24 12:05 Poky on "standard" PC Gary Thomas 2011-01-24 12:39 ` Richard Purdie 2011-01-24 22:54 ` Darren Hart 2011-01-25 12:08 ` Gary Thomas 2011-01-25 13:45 ` Bruce Ashfield 2011-01-25 16:37 ` Gary Thomas 2011-01-25 16:40 ` Bruce Ashfield 2011-01-25 16:45 ` Gary Thomas 2011-01-25 20:16 ` Saul Wold 2011-01-25 22:52 ` Richard Purdie 2011-01-26 0:30 ` Darren Hart 2011-01-26 1:37 ` Gary Thomas 2011-01-26 19:31 ` Darren Hart
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.