From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: freetype-config broken?
Date: Wed, 30 Jul 2014 11:57:52 -0600 [thread overview]
Message-ID: <53D93220.4030901@mlbassoc.com> (raw)
In-Reply-To: <CAMKF1srm+0up4YsN2u6UQrmO948NHqk1YZAwhx_kaX22e-h=zQ@mail.gmail.com>
On 2014-07-30 11:32, Khem Raj wrote:
> On Wed, Jul 30, 2014 at 9:37 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>> The behaviour of 'freetype-config' (from freetype-native) has
>> changed since this commit:
>> commit 3476a49b10093c58b2f89e3d9a8527224f1bd7f6
>> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
>> Date: Thu May 22 10:59:33 2014 +0100
>> binconfig-disabled: Add class and use
>>
>> This is breaking my build of mplayer which uses freetype-config
>> to determine how to use the freetype library (in ./configure)
>>
>> The comment in the commit indicates that this is an improvement
>> and the path forward, but I don't see how to change the recipes
>> (and scripts, etc) that rely on this functionality to work in
>> this new mode.
>>
>> Any suggestions?
>>
> add AM_INIT_AUTOMAKE([foreign]) to the configure.in or configure.ac
I don't see how your suggestion helps. This package (mplayer) doesn't
use autotools - it has a hand coded configure script, so there is
no configure.{in,ac}
I also looked through the logs and didn't see any recipe which uses
a package that is now marked as binconfig-disabled as to how it
solves the problem. A pointer/example would really be appreciated.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-07-30 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 16:37 freetype-config broken? Gary Thomas
2014-07-30 17:29 ` Martin Jansa
2014-07-30 17:32 ` Khem Raj
2014-07-30 17:57 ` Gary Thomas [this message]
2014-07-30 19:33 ` Martin Jansa
2014-07-30 20:04 ` Gary Thomas
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=53D93220.4030901@mlbassoc.com \
--to=gary@mlbassoc.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