From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Cc: Alex Bennee <ajb@cbnl.com>
Subject: Re: [PATCH 1/2] freetype: include perl-native dependancy
Date: Thu, 12 Aug 2010 11:57:04 -0700 [thread overview]
Message-ID: <4C644400.5050806@mentor.com> (raw)
In-Reply-To: <AANLkTin-=7FuDRhnt77hy_tfvBM5xCKkQcx2EWBuc14u@mail.gmail.com>
Alex Bennee wrote:
> On 12 August 2010 18:04, Tom Rini <tom_rini@mentor.com> wrote:
>> kernel-hacker@bennee.com wrote:
>>> From: Alex Bennee <ajb@cbnl.com>
>>>
>>> Freetype requires a native perl to build during it's configure step.
>>> I'm unsure how it built before unless other uses had brought in
>>> perl-native through another dependancy (our GTK setup is fairly
>>> minimal).
>>>
>>> Signed-off-by: Alex Bennee <ajb@cbnl.com>
>> OE assumes that there is a host perl already. perl-native is mainly
>> provided for some very special cases (such as building perl for the target).
>
> How odd, I couldn't get configure to run without a perl-native. Maybe
> because I was building for i686 on an x86_64. I guess it relegates
> that patch to a "works for us" status.
So, were you building for say MACHINE=qemux86
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-08-12 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 15:35 A few fixes (resend, hopefully not munged this time) kernel-hacker
2010-08-12 15:35 ` [PATCH 1/2] freetype: include perl-native dependancy kernel-hacker
2010-08-12 17:04 ` Tom Rini
2010-08-12 17:23 ` Alex Bennee
2010-08-12 18:57 ` Tom Rini [this message]
2010-08-12 15:35 ` [PATCH 2/2] recode: Fix configure step kernel-hacker
2010-08-12 17:05 ` Tom Rini
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=4C644400.5050806@mentor.com \
--to=tom_rini@mentor.com \
--cc=ajb@cbnl.com \
--cc=openembedded-devel@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 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.