From: Tom Zanussi <tom.zanussi@intel.com>
To: v sailaja <vsailub4u@gmail.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Problem in linux-yocto kernel 2.6.37 configuration while building with sugarbay machine
Date: Tue, 05 Apr 2011 09:10:04 -0500 [thread overview]
Message-ID: <1302012604.23110.374.camel@elmorro> (raw)
In-Reply-To: <BANLkTi=bhCcOF6Mr3v79s3aZ9Ae=+pKRLA@mail.gmail.com>
On Tue, 2011-04-05 at 03:06 -0700, v sailaja wrote:
>
> Hi,
>
> I am trying to build poky image "piky-image-minimal-live" for
> "sugarbay" machine with linux-yocto kernel 2.6.37 kernel which
> supports the sandy-bridge.
>
> I clone poky source as git clone git://git.pokylinux.org/poky.git
>
> And cloned for meta-intel from
> http://git.pokylinux.org/cgit/cgit.cgi/meta-intel
>
> Also made entries in bblayers.conf as "meta-intel /meta-sugarbay"
>
> My machine is 64bit one.
>
> I made changes in sugarbay.conf, for building "i586" , as follows
>
> TARGET_ARCH = "i586"
> TARGET_CC_ARCH = "-m32"
> #TARGET_CC_ARCH = "-m64"
>
> I tried to build it for both 32 and 64 bit.
>
> I got the common error both time.
>
> Error log:1
>
>
> ---------------------------------------------*********************************************-----------------------------------
> This BSP sets 24 kernel options that are possibly non-hardware
> related.
> The full list can be found in your workspace at:
> /home/sailaja/new-poky/x86_64/
> poky/build/tmp/work/sugarbay-poky-linux/linux-yocto-2.6.37+git1
> +e2cabadc059ad8d91f7e4a023106620d93abd23a_1
> +2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r16/linux/meta/cfg/yocto/standard/common-pc-64/sugarbay/specified_non_hdw.cfg
>
> WARNING: There were 103 hardware options requested that do not
> have a corresponding value present in the final ".config"
> file.
> This probably means you aren't getting the config you wanted.
> The full list can be found in your workspace at:
> /home/sailaja/new-poky/x86_64/poky/build/tmp/work/sugarbay-poky-linux/linux-yocto-2.6.37+git1+e2cabadc059ad8d91f7e4a023106620d93abd23a_1+2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r16/linux/meta/cfg/yocto/standard/common-pc-64/sugarbay/mismatch.cfg
>
> Waiting a second to make sure you get a chance to see this...
> NOTE: package linux-yocto-2.6.37+git1
> +e2cabadc059ad8d91f7e4a023106620d93abd23a_1
> +2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r16: task
> do_kernel_configcheck: Succeeded
> NOTE: Running task 960 of 1998 (ID:
> 857, /home/sailaja/new-poky/poky/meta/recipes-kernel/linux/linux-yocto_git.bb, do_compile)
> NOTE: package linux-yocto-2.6.37+git1
> +e2cabadc059ad8d91f7e4a023106620d93abd23a_1
> +2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r16: task do_compile:
> Started
> ERROR:
> '/home/sailaja/new-poky/poky/meta/recipes-kernel/linux/linux-yocto_git.bb' failed
>
>
> | /home/sailaja/new-poky/poky/build/tmp/work/sugarbay-poky-linux/linux-yocto-2.6.37+git1+e2cabadc059ad8d91f7e4a023106620d93abd23a_1+2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r16/linux/kernel/bounds.c:1:0: error: code model 'kernel' not supported in the 32 bit mode
> | /home/sailaja/new-poky/poky/build/tmp/work/sugarbay-poky-linux/linux-yocto-2.6.37+git1+e2cabadc059ad8d91f7e4a023106620d93abd23a_1+2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r16/linux/kernel/bounds.c:1:0: sorry, unimplemented: 64-bit mode not compiled in
> | make[3]: *** [kernel/bounds.s] Error 1
> | make[2]: *** [prepare0] Error 2
> | make[2]: *** Waiting for unfinished jobs....
> | make[2]: *** [scripts] Error 2
> | make[1]: *** [sub-make] Error 2
> | make: *** [all] Error 2
> | FATAL: oe_runmake failed
> | ERROR: Function 'do_compile' failed
> (see /home/sailaja/new-poky/poky/build/tmp/work/sugarbay-poky-linux/linux-yocto-2.6.37+git1+e2cabadc059ad8d91f7e4a023106620d93abd23a_1+2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r16/temp/log.do_compile.29452 for further information)
> NOTE: package linux-yocto-2.6.37+git1
> +e2cabadc059ad8d91f7e4a023106620d93abd23a_1
> +2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r16: task do_compile: Failed
> ERROR: Task 857
> (/home/sailaja/new-poky/poky/meta/recipes-kernel/linux/linux-yocto_git.bb, do_compile) failed with exit code '1'
> ---------------******************************-------------------
>
> I thought, the reason for this error is
> As My machine is 64 bit one. It is configured for the default
> configurations i.e., it is using the x86_64_defconfig and 64 bit is
> enabled in the .config file.
> This is because of misconfiguration.
>
> I configured my kernel.
>
> My build is done. But I am getting an error while building the rootfs.
>
> Error log:2
>
> ---------------------------------------********************************************-------------------------------------------------
> NOTE: package poky-image-minimal-live-1.0-r0: task do_bootimg: Started
> ERROR:
> '/home/sailaja/new-poky/poky/meta/recipes-core/images/poky-image-minimal-live.bb' failed
> ERROR: Function 'build_boot_bin' failed
> (see /home/sailaja/new-poky/poky/build/tmp/work/snb-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.32052 for further information)
> ERROR: Logfile of failure stored
> in: /home/sailaja/new-poky/poky/build/tmp/work/snb-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.32052
> Log data follows:
> | install: cannot stat
> `/home/sailaja/new-poky/poky/build/tmp/sysroots/sugarbay/kernel/bzImage': No such file or directory
> | ERROR: Function 'build_boot_bin' failed
> (see /home/sailaja/new-poky/poky/build/tmp/work/snb-poky-linux/poky-image-minimal-live-1.0-r0/temp/log.do_bootimg.32052 for further information)
> NOTE: package poky-image-minimal-live-1.0-r0: task do_bootimg: Failed
> ERROR: Task 8
> (/home/sailaja/new-poky/poky/meta/recipes-core/images/poky-image-minimal-live.bb, do_bootimg) failed with exit code '1' Error
>
> -------------------------------------------------************************************************------------------------------
>
>
> Why it is happening?
> Please Can anyone help me in finding the solution.
>
I've seen this too with master - bzImage is built ok and exists, but
doesn't get copied or linked to in sysroots and fails.
I would suggest using poky/bernard instead of poky/master. Using
meta-intel/master should still be ok.
FYI, I've put a transcript of a successful build, from git checkout to
image, here:
https://wiki.yoctoproject.org/wiki/Transcript:_from_git_checkout_to_meta-intel_BSP
You should be able to just substitute 'sugarbay' for 'fishriver' to
build for sugarbay...
hth,
Tom
>
>
>
>
>
>
> --
> Thanks & Regards,
> SAI
>
prev parent reply other threads:[~2011-04-05 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 10:28 Problem in linux-yocto kernel 2.6.37 configuration while building with sugarbay machine v sailaja
2011-03-31 12:37 ` Bruce Ashfield
2011-03-31 12:55 ` v sailaja
2011-03-31 12:58 ` Bruce Ashfield
[not found] ` <AANLkTinWqFSqg8KOy1WVZHEpvqcsraZPna8JUdDLeXqy@mail.gmail.com>
[not found] ` <AANLkTi=z3FRBiLs2iCLLDhU3q6AvnbXiEGbsbNczykMN@mail.gmail.com>
2011-04-01 12:01 ` v sailaja
2011-04-05 10:06 ` v sailaja
2011-04-05 14:10 ` Tom Zanussi [this message]
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=1302012604.23110.374.camel@elmorro \
--to=tom.zanussi@intel.com \
--cc=poky@yoctoproject.org \
--cc=vsailub4u@gmail.com \
/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.