Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>,
	Stefan Stanacar <stefanx.stanacar@intel.com>,
	<openembedded-core@lists.openembedded.org>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Stefan Stanacar : recipes-bsp: Add gummiboot recipe
Date: Thu, 27 Mar 2014 14:08:44 +0800	[thread overview]
Message-ID: <5333C06C.6020900@windriver.com> (raw)
In-Reply-To: <20140326201833.GI3709@jama>


I met a similar error, maybe we can add:
COMPATIBLE_HOST = "(x86_64.*|i.86.*)-linux"

to gummiboot_git.bb to fix the problem.

I will send a patch for it, and fix another gnu-efi error.

// Robert

On 03/27/2014 04:18 AM, Martin Jansa wrote:
> On Tue, Mar 11, 2014 at 04:23:55PM +0000, git@git.openembedded.org wrote:
>> Module: openembedded-core.git
>> Branch: master
>> Commit: 8f95d0598c31fff76e2a58fecb6c96197121a044
>> URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=8f95d0598c31fff76e2a58fecb6c96197121a044
>>
>> Author: Stefan Stanacar <stefanx.stanacar@intel.com>
>> Date:   Fri Feb 21 12:17:35 2014 +0200
>
> COMPATIBLE_HOST = "(x86_64.*|i.86.*)-linux"
>
> matching with gnu-efi on which it depends?
>
> Right now it causes ugly error in "bitbake world"
>
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing PROVIDES 'gnu-efi' (but /home/jenkins/oe/shr-core-branches/shr-core/openembedded-core/meta/recipes-bsp/gummiboot/gummiboot_git.bb DEPENDS on or otherwise requires it)
> ERROR: gnu-efi was skipped: incompatible with host arm-oe-linux-gnueabi (not in COMPATIBLE_HOST)
> ERROR: Nothing RPROVIDES 'gummiboot-dev' (but /home/jenkins/oe/shr-core-branches/shr-core/openembedded-core/meta/recipes-bsp/gummiboot/gummiboot_git.bb RDEPENDS on or otherwise requires it)
> ERROR: No eligible RPROVIDERs exist for 'gummiboot-dev'
> NOTE: Runtime target 'gummiboot-dev' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['gummiboot-dev']
> ERROR: Nothing RPROVIDES 'gummiboot' (but /home/jenkins/oe/shr-core-branches/shr-core/openembedded-core/meta/recipes-bsp/gummiboot/gummiboot_git.bb RDEPENDS on or otherwise requires it)
> ERROR: No eligible RPROVIDERs exist for 'gummiboot'
> NOTE: Runtime target 'gummiboot' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['gummiboot']
>
>
>>
>> recipes-bsp: Add gummiboot recipe
>>
>> gummiboot is a simple UEFI boot manager.
>>
>> Recipe imported from meta-intel with these changes:
>>   - drop PR and update configure options
>>   - upgraded to latest version
>>
>> A couple of notes:
>>   - If you wish you can install the gummiboot package on the target and
>> use 'gummiboot install' to add the payload to the ESP (see gummiboot --help,
>> just make sure the ESP partition has the boot flag on as gummiboot won't accept it
>> otherwise). However the point of this recipe is to be used by bootimg.bbclass and
>> generate images with gummiboot instead of grub-efi.
>>   - You need a kernel which has CONFIG_EFI_STUB=y at least
>>   - The default linux-yocto kernel config does not enable that, easiest way
>> to enable is to build with KERNEL_FEATURES_append = " cfg/efi-ext" in local.conf
>>
>> Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com>
>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>>
>> ---
>>
>>   meta/recipes-bsp/gummiboot/gummiboot_git.bb | 25 +++++++++++++++++++++++++
>>   1 file changed, 25 insertions(+)
>>
>> diff --git a/meta/recipes-bsp/gummiboot/gummiboot_git.bb b/meta/recipes-bsp/gummiboot/gummiboot_git.bb
>> new file mode 100644
>> index 0000000..5868a23
>> --- /dev/null
>> +++ b/meta/recipes-bsp/gummiboot/gummiboot_git.bb
>> @@ -0,0 +1,25 @@
>> +SUMMARY = "Gummiboot is a simple UEFI boot manager which executes configured EFI images."
>> +HOMEPAGE = "http://freedesktop.org/wiki/Software/gummiboot"
>> +
>> +LICENSE = "LGPLv2.1"
>> +LIC_FILES_CHKSUM = "file://LICENSE;md5=4fbd65380cdd255951079008b364516c"
>> +
>> +DEPENDS = "gnu-efi util-linux"
>> +
>> +inherit autotools
>> +inherit deploy
>> +
>> +PV = "43+git${SRCPV}"
>> +SRCREV = "4062c51075ba054d4949c714fe06123f9ad3097d"
>> +SRC_URI = "git://anongit.freedesktop.org/gummiboot"
>> +
>> +S = "${WORKDIR}/git"
>> +
>> +EXTRA_OECONF = "--disable-manpages --with-efi-includedir=${STAGING_INCDIR} \
>> +                --with-efi-ldsdir=${STAGING_LIBDIR} \
>> +                --with-efi-libdir=${STAGING_LIBDIR}"
>> +
>> +do_deploy () {
>> +        install ${B}/gummiboot*.efi ${DEPLOYDIR}
>> +}
>> +addtask deploy before do_build after do_compile
>>
>> --
>> _______________________________________________
>> Openembedded-commits mailing list
>> Openembedded-commits@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-commits
>
>
>


      reply	other threads:[~2014-03-27  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140311162355.554E95039B@opal>
2014-03-26 20:18 ` [oe-commits] Stefan Stanacar : recipes-bsp: Add gummiboot recipe Martin Jansa
2014-03-27  6:08   ` Robert Yang [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=5333C06C.6020900@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-commits@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=stefanx.stanacar@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox