[OE-core] [RFC PATCH 1/5] grub-efi-native: New recipe to build GRUB EFI images

Koen Kooi koen at dominion.thruhere.net
Tue Nov 29 09:16:16 UTC 2011


Op 29 nov. 2011, om 09:58 heeft Darren Hart het volgende geschreven:

> 
> 
> On 11/29/2011 12:22 AM, Koen Kooi wrote:
>> 
>> Op 29 nov. 2011, om 09:03 heeft Darren Hart het volgende geschreven:
>> 
>>> On 11/25/2011 02:57 PM, Darren Hart wrote:
>>>> 
>>>> 
>>>> On 11/24/2011 12:05 AM, Darren Hart wrote:
>>>>> Add a recipe to build the GRUB efi images. This recipe is written as
>>>>> a native recipe as the resulting GRUB utils are required to assemble
>>>>> the final image. Rather than build a native and a target recipe (and
>>>>> increase build times), this recipe builds the utils for the host and
>>>>> passes an appropriate --target argument to the GRUB configure script
>>>>> to build the modules for the target arch. The only output of this
>>>>> recipe is an EFI image in the deploy directory.
>>>> 
>>>> The grub-help list came through with an alternative approach:
>>>> 
>>>> "./configure CC=powerpc-linux-gcc  --host=ppc-linux-gnu --target=i386
>>>> --with-platform=pc TARGET_CC=i386-linux-gcc"
>>>> 
>>>> This would allow for building on a host of arch ppc for a target of arch
>>>> i386.
>>>> 
>>>> Would it be preferable then to build this as a target package and
>>>> manipuate the configure flags to use the BUILD_CC ? I presume a similar
>>>> PN rename would be desirable to account for the HOST component of the
>>>> build as I used here for the TARGET on the -native version?
>>> 
>>> I have been working on trying to get this working as a target recipe. I've
>>> resolved a number of issues, but something is still biting me and I haven't been
>>> able to sort out what. I would really appreciate a few more sets of eyes on
>>> this.
>>> 
>>> I have pushed my dvhart/efi/dev branch to poky-contrib for reference:
>>> 
>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/?h=dvhart/efi/dev
>>> 
>>> When building this recipe
>> 
>> This is against poky, so I can't build it. If it was against
>> OE-core, like one would expect on the OE-core mailing list,
>> I could build it.
> 
> OK, fair enough.
> 
> git://git.infradead.org/srv/git/users/dvhart/oe-core.git dvhart/efi/dev

I get:

$ git fetch git://git.infradead.org/srv/git/users/dvhart/oe-core.git
fatal: The remote end hung up unexpectedly

regards,

Koen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20111129/ab59f3f6/attachment-0002.sig>


More information about the Openembedded-core mailing list