From: Darren Hart <dvhart@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH] grub-efi: Do not use help2man
Date: Mon, 02 Jul 2012 18:03:39 -0700 [thread overview]
Message-ID: <4FF244EB.8040809@linux.intel.com> (raw)
In-Reply-To: <1341261067.23146.269.camel@ted>
On 07/02/2012 01:31 PM, Richard Purdie wrote:
> On Mon, 2012-07-02 at 13:09 -0700, Darren Hart wrote:
>> +Index: grub-1.99/configure
>> +===================================================================
>> +--- grub-1.99.orig/configure
>> ++++ grub-1.99/configure
>
> Isn't configure regenerated so we don't need this second bit patching
> configure, just configure.ac?
It wasn't in my tests. I tried again in master with:
$ bitbake grub-efi-i586 native -c cleanall
$ bitbake grub-efi-i586 native -d devshell
performs fetch, unpack, patch
# edited configure.ac and left configure alone
$ bitbake grub-efi-i586 native
Fails in the same way and configure does not reflect the changes from
configure.ac. This is what I would expect as ./autogen.sh should
typically only be run when building from the RCS sources and not release
tarballs.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-07-03 1:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 20:09 [RFC PATCH] grub-efi: Do not use help2man Darren Hart
2012-07-02 20:31 ` Richard Purdie
2012-07-03 1:03 ` Darren Hart [this message]
2012-07-02 23:42 ` Khem Raj
2012-07-03 0:54 ` Darren Hart
2012-07-03 4:28 ` Khem Raj
2012-07-03 19:03 ` 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=4FF244EB.8040809@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@linuxfoundation.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