From: jhuang0 <jackie.huang@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] grub-efi: change to generate EFI image in target package
Date: Fri, 22 Nov 2013 14:29:26 +0800 [thread overview]
Message-ID: <528EF9C6.6030202@windriver.com> (raw)
In-Reply-To: <1385096527.3614.32.camel@dvhart-mobl4.amr.corp.intel.com>
On 11/22/2013 1:02 PM, Darren Hart wrote:
> On Fri, 2013-11-22 at 12:49 +0800, jhuang0 wrote:
>>
>> On 11/22/2013 10:45 AM, Darren Hart wrote:
>>> On Wed, 2013-11-20 at 09:40 +0800, jackie.huang@windriver.com wrote:
>>>> From: Jackie Huang <jackie.huang@windriver.com>
>>>>
>>>> It's not a good idea to generate the target EFI image in
>>>> a native packge,
>>>
>>> This was admittedly a hack when I wrote it...
>>>
>>>> it would be a problem when build a 64bit
>>>> target on 32bit host.
>>>
>>> I build 32b on a 64b host regularly, why is it a problem the other way
>>> around?
>>>
>>> There is infrastructure in place to specify the target architecture for
>>> the grub efi binary and the modules. The 32b compiler should be able to
>>> do -m64 just as the 64b compiler can do -m32.
>>
>> It should be, but for most 32bit linux distributions, gcc is not
>> compiled for supporting 64bit cross compiling.
>
> Thanks for the detail - including this information in the justification
> would be a good idea so anyone looking at the commit log can understand
> why it was necessary.
>
>
>>>> -do_install[noexec] = "1"
>>>> -do_populate_sysroot[noexec] = "1"
>>>> +FILES_${PN}-dbg += "${libdir}/${BPN}/${GRUB_TARGET}-efi/.debug"
>>>
>>> Technically this is an independent functional change...
>>
>> You mean it should be in a separate commit?
>
> I was thinking so, but I see Saul raised it as an issue with V2, so
> please disregard this comment, it's fine.
>
> I'd like to see a blurb added to the commit message stating the bit
> about gcc not having support in some distributions (debian/ubuntu do
> have it for example, but later versions require the compat package or
> some such). The fact that some don't is enough though, and your solution
> is cleaner and more consistent with bitbake recipe conventions anyway.
I will add these information to the commit log in v4.
Thanks,
Jackie
>
> Thanks for keeping at it, this is a good improvement.
>
--
Jackie Huang
WIND RIVER | China Development Center
MSN:jackielily@hotmail.com
Tel: +86 8477 8594
Mobile: +86 138 1027 4745
next prev parent reply other threads:[~2013-11-22 6:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 1:40 [PATCH 0/2 v3] grub-efi: change to generate EFI image in target package jackie.huang
2013-11-20 1:40 ` [PATCH 1/2] " jackie.huang
2013-11-22 2:45 ` Darren Hart
2013-11-22 4:49 ` jhuang0
2013-11-22 5:02 ` Darren Hart
2013-11-22 6:29 ` jhuang0 [this message]
2013-11-20 1:40 ` [PATCH 2/2] grub-efi: allow compilation without large model support jackie.huang
2013-11-22 2:49 ` Darren Hart
2013-11-22 3:37 ` jhuang0
2013-11-22 5:04 ` Darren Hart
2013-11-22 6:18 ` jhuang0
-- strict thread matches above, loose matches on Subject: below --
2013-11-22 7:23 [PATCH 0/2 v4] grub-efi: change to generate EFI image in target package jackie.huang
2013-11-22 7:23 ` [PATCH 1/2] " jackie.huang
2013-11-22 10:00 [PATCH 0/2 v5] " jackie.huang
2013-11-22 10:00 ` [PATCH 1/2] " jackie.huang
2013-11-22 18:52 ` Darren Hart
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=528EF9C6.6030202@windriver.com \
--to=jackie.huang@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox