From: Darren Hart <darren.hart@intel.com>
To: Josef Ahmad <josef.ahmad@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: qemu EFI build failure
Date: Thu, 12 Jan 2012 13:19:56 -0800 [thread overview]
Message-ID: <4F0F4E7C.9030506@intel.com> (raw)
In-Reply-To: <4F0F2627.3010004@linux.intel.com>
On 01/12/2012 10:27 AM, Darren Hart wrote:
>
>
> On 01/12/2012 08:19 AM, Josef Ahmad wrote:
>> I tried to build a qemux86 EFI image, by setting:
>> - in my local.conf: IMAGE_FSTYPES += "live"
>> - in poly/meta/conf/machine/qemux86.conf: MACHINE_FEATURES += "efi"
>>
>
> I haven't tried live images with QEMU. For one thing, they aren't really
> necessary as you can specify all the boot parameters on the qemu command
> line. Is there are reason you want to use the live image specifically?
>
> Also, in order to properly test EFI in QEMU, you will need to use an EFI
> BIOS - I believe you're aware of this already - but this isn't currently
> supported by the runqemu scripts that ship with yocto.
>
>> The build gave me the following error:
>
>
> I'll do some test builds - it isn't clear to me what is going on here.
>
> <snip>
>
>>
>>
>> Has anyone encountered the same error? I'm not sure I set up the
>> correct configuration. Also, is there another way to append "efi" to
>> MACHINE_FEATURES rather than by modifying qemux86.conf?
>
> You should be able to do something like:
> MACHINE_FEATURES_append_qemux86 = "efi"
>
> Note that you will also need to enable the efi support in the kernel,
> which is done with the KERNEL_FEATURES variable, something like:
> KERNEL_FEATURES_append_qemux86 = "conf/efi-ext.scc"
>
> Either of these can be set in your local.conf.
>
More accurately:
MACHINE_FEATURES_append_qemux86=" efi pcbios"
KERNEL_FEATURES_append_qemux86=" cfg/efi-ext.scc"
IMAGE_FSTYPES += "live"
With these added to local.conf and building for qemux86 I see the same
configure failures reported by Kishore and Josef:
| ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
| acinclude.m4:363: grub_CHECK_STACK_ARG_PROBE is expanded from...
I've discussed in IRC with Nitin and he thinks this may be related to
the automake update and is looking into it.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-01-12 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 16:19 qemu EFI build failure Josef Ahmad
2012-01-12 18:27 ` Darren Hart
2012-01-12 21:19 ` Darren Hart [this message]
2012-01-12 21:28 ` Bodke, Kishore K
2012-01-12 21:39 ` Darren Hart
2012-01-12 22:31 ` Kamble, Nitin A
2012-01-12 22:33 ` Kamble, Nitin A
2012-01-16 22:00 ` Kamble, Nitin A
2012-01-16 23:03 ` Darren Hart
2012-01-18 12:36 ` Josef Ahmad
2012-01-18 12:38 ` Josef Ahmad
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=4F0F4E7C.9030506@intel.com \
--to=darren.hart@intel.com \
--cc=josef.ahmad@intel.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.