From: Saul Wold <sgw@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: [PATCH][meta-intel] grub: remove the dependency on freetype, disable grub-mkfont
Date: Thu, 01 Sep 2011 10:19:49 -0700 [thread overview]
Message-ID: <4E5FBEB5.8080407@linux.intel.com> (raw)
In-Reply-To: <24a30eaf49c25c0b5d8b5d7405691c6c1b67588d.1314844442.git.dvhart@linux.intel.com>
Seeing this change reminded me that we really should move grub_1.98 to
oe-core, is there any objection to this? Any reason this should not be
part of oe-core to support general x86_64 machines?
Sau!
On 08/31/2011 07:34 PM, Darren Hart wrote:
> Grub's configure task was picking up the host freetype libraries if
> bitbake hadn't gotten around building freetype yet. We could add a
> dependency on freetype, but it's only used for the optional grub-mkfont
> utility which we don't really need.
>
> Disable grub-mkfont via EXTRA_OECONF, removing the dependency on freetype.
>
> Testing: core-image-minimal build and install on sugarbay.
>
> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
> Tested-by: Tom Zanussi<tom.zanussi@intel.com>
> ---
> common/recipes-bsp/grub/grub_1.98.bb | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/common/recipes-bsp/grub/grub_1.98.bb b/common/recipes-bsp/grub/grub_1.98.bb
> index 0cd3a40..802733f 100644
> --- a/common/recipes-bsp/grub/grub_1.98.bb
> +++ b/common/recipes-bsp/grub/grub_1.98.bb
> @@ -24,7 +24,7 @@ SRC_URI = "ftp://alpha.gnu.org/gnu/grub/grub-${PV}.tar.gz \
> inherit autotools
> inherit gettext
>
> -EXTRA_OECONF = "--with-platform=pc --target=i386"
> +EXTRA_OECONF = "--with-platform=pc --target=i386 --disable-grub-mkfont"
>
> do_configure() {
> oe_runconf
next prev parent reply other threads:[~2011-09-01 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 2:34 [PATCH][meta-intel] grub: remove the dependency on freetype, disable grub-mkfont Darren Hart
2011-09-01 17:19 ` Saul Wold [this message]
2011-09-03 5:09 ` Darren Hart
2011-09-01 20:55 ` 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=4E5FBEB5.8080407@linux.intel.com \
--to=sgw@linux.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.