From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Brian Karcz <briank@RUSSOUND.COM>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-atmel] at91sam9x5ek: "no machine record defined" failure for core-image-minimal
Date: Fri, 9 May 2014 09:54:31 -0400 [thread overview]
Message-ID: <536CDE17.40806@windriver.com> (raw)
In-Reply-To: <f9f1c263a9ab4a3085bf1a696f31aec6@HERMES.RUSSOUND.com>
On 14-05-09 09:44 AM, Brian Karcz wrote:
> Hi,
>
> Not sure if this is the correct place to email this, but I’ve seen a few
> other meta-atmel references so I figured I’d give it a shot.
>
> I’m attempting to setup a core-image-minimal build using the guidelines
> in the meta-atmel README for the at91sam9x5ek machine type. When the
> kernel build goes to link, I get a “no machine record defined” error. Is
> this something others are seeing in the meta-atmel demo builds?
>
> It’s a pretty benign build setup according to the README:
>
> git clone git://git.yoctoproject.org/poky
>
> cd poky
>
> git checkout dora-10.0.1 -b dora-10.0.1
>
> git clone git://git.openembedded.org/meta-openembedded
>
> cd meta-openembedded
>
> git checkout 6572316557e742c2dc93848e4d560242bf0c3995 -b my_branch
>
> cd ..
>
> git clone http://github.com/linux4sam/meta-atmel
>
> source oe-init-build-env /workspace/build-atmel
>
> modify local.conf:
>
> MACHINE ??= ”at91sam9x5ek”
>
> PACKAGE_CLASSES ?= “package_ipk”
>
> modify bblayers.conf:
>
> BBLAYERS ?= " \
>
> /opt/poky/meta-atmel \
>
> /opt/poky/meta \
>
> /opt/poky/meta-yocto \
>
> /opt/poky/meta-yocto-bsp \
>
> /opt/poky/meta-openembedded/meta-oe \
>
> /opt/poky/meta-openembedded/meta-networking \
>
> "
>
> bitbake core-image-minimal
>
> Setting this up, I get the following build configuration and error:
>
> /workspace/build-atmel$ bitbake core-image-minimal
>
> Loading cache: 100%
> |######################################################################################|
> ETA: 00:00:00
>
> Loaded 1782 entries from dependency cache.
>
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
>
> BB_VERSION = "1.20.0"
>
> BUILD_SYS = "x86_64-linux"
>
> NATIVELSBSTRING = "Ubuntu-12.04"
>
> TARGET_SYS = "arm-poky-linux-gnueabi"
>
> MACHINE = "at91sam9x5ek"
>
> DISTRO = "poky"
>
> DISTRO_VERSION = "1.5.1"
>
> TUNE_FEATURES = "armv5 thumb dsp"
>
> TARGET_FPU = "soft"
>
> meta-atmel = "master:269066a8128d1e767deee64854a142e67451a5f2"
>
> meta
>
> meta-yocto
>
> meta-yocto-bsp = "dora-10.0.1:8e410e9e46e3335458a7747cdd32e05f5c19ccbb"
>
> meta-oe
>
> meta-networking = "my_branch:6572316557e742c2dc93848e4d560242bf0c3995"
>
> NOTE: Preparing runqueue
>
> NOTE: Executing SetScene Tasks
>
> NOTE: Executing RunQueue Tasks
>
> ERROR: Function failed: do_compile (log file is located at
> /workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-yocto-custom/3.10+AUTOINC+68f2c28207-r5/temp/log.do_compile.2291)
>
> ERROR: Logfile of failure stored in:
> /workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-yocto-custom/3.10+AUTOINC+68f2c28207-r5/temp/log.do_compile.2291
>
> Log data follows:
>
> | DEBUG: Executing shell function do_compile
>
> | NOTE: make -j 2 zImage CC=arm-poky-linux-gnueabi-gcc
> -mno-thumb-interwork -marm LD=arm-poky-linux-gnueabi-ld.bfd
>
> | GEN
> /workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-yocto-custom/3.10+AUTOINC+68f2c28207-r5/linux-at91sam9x5ek-standard-build/Makefile
>
> | CHK include/generated/uapi/linux/version.h
>
> | CHK include/generated/utsrelease.h
>
> | Using
> /workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-yocto-custom/3.10+AUTOINC+68f2c28207-r5/linux
> as source for kernel
>
> | make[3]: `include/generated/mach-types.h' is up to date.
>
> | CC scripts/mod/devicetable-offsets.s
>
> | GEN scripts/mod/devicetable-offsets.h
>
> | HOSTCC scripts/mod/file2alias.o
>
> | CALL
> /workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-yocto-custom/3.10+AUTOINC+68f2c28207-r5/linux/scripts/checksyscalls.sh
>
> | HOSTLD scripts/mod/modpost
>
> | CHK include/generated/compile.h
>
> | LINK vmlinux
>
> | LD vmlinux.o
>
> | MODPOST vmlinux.o
>
> | GEN .version
>
> | CHK include/generated/compile.h
>
> | UPD include/generated/compile.h
>
> | CC init/version.o
>
> | LD init/built-in.o
>
> | arm-poky-linux-gnueabi-ld.bfd: no machine record defined
>
> | make[2]: *** [vmlinux] Error 1
>
> | make[1]: *** [sub-make] Error 2
>
> | make: *** [all] Error 2
>
> | ERROR: oe_runmake failed
>
> | WARNING: exit code 1 from a shell command.
>
> | ERROR: Function failed: do_compile (log file is located at
> /workspace/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-yocto-custom/3.10+AUTOINC+68f2c28207-r5/temp/log.do_compile.2291)
>
> ERROR: Task 208
> (/opt/poky/meta-atmel/recipes-kernel/linux/linux-yocto-custom_3.10.bb,
> do_compile) failed with exit code '1'
>
> NOTE: Tasks Summary: Attempted 793 tasks of which 785 didn't need to be
> rerun and 1 failed.
>
> Waiting for 0 running tasks to finish:
>
> Summary: 1 task failed:
>
> /opt/poky/meta-atmel/recipes-kernel/linux/linux-yocto-custom_3.10.bb,
> do_compile
>
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
> Any thoughts on what might be missing from the README or my
> implementation of it to get this demo build working?
Can you confirm that the final .config for the board has the machine
definitions that you'd expect for the board ?
Bruce
>
> Thanks,
>
> Brian
>
>
>
next prev parent reply other threads:[~2014-05-09 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 13:44 [meta-atmel] at91sam9x5ek: "no machine record defined" failure for core-image-minimal Brian Karcz
2014-05-09 13:54 ` Bruce Ashfield [this message]
2014-05-09 14:58 ` Brian Karcz
2014-05-09 18:41 ` Bruce Ashfield
2014-05-09 19:31 ` Bryan Evenson
2014-05-09 19:49 ` Brian Karcz
2014-05-09 20:35 ` Bryan Evenson
2014-05-09 19:34 ` Brian Karcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=536CDE17.40806@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=briank@RUSSOUND.COM \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.