From: Martin Jansa <martin.jansa@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: freetype-config broken?
Date: Wed, 30 Jul 2014 21:33:51 +0200 [thread overview]
Message-ID: <20140730193351.GU16445@jama> (raw)
In-Reply-To: <53D93220.4030901@mlbassoc.com>
[-- Attachment #1: Type: text/plain, Size: 2196 bytes --]
On Wed, Jul 30, 2014 at 11:57:52AM -0600, Gary Thomas wrote:
> 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.
meta-oe:
6898dae64e79fa81c3b032cb314e3c2d6f2c6e0d
d7363984b83c938db6f0a16ca8732bed69ca8acb
141aedb403e4bb91dac6ffb109ee74dfaee59f81
18ccf18ee4949b785e240d9f8f8983c6554dd4e9
09566d518a56a413303d7d13d496254b467c635b
6cc47fb2b007504be3e32698ed14b1bebc981526
oe-core:
b550572bdad318aed02230496721430eec89c937
d2457880e7bb08b9c2f8d60e70b1d59ed84e9da9
fe277bf0a61d5d7787dba699ee1ed4d979ba5cff
4a971a90988435902a4a8dd9c721d440cd80c0bd
ffffc627b21a3cf8b407d16a437793b5fddf7127
74d73cf1e4607cb313b5e4c7138b555d5999a46d
f0479e60b660778ab27b946d426daa17a08a28ea
437ad15de308769c9251a37ed41dabed5653fc96
17e5793847601d2aeb497ffe14871df65543abfb
ff573270f7e87296840911189fd2087a1bc597f7
It's really not so hard to search for "-config" in git log.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-07-30 19:33 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
2014-07-30 19:33 ` Martin Jansa [this message]
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=20140730193351.GU16445@jama \
--to=martin.jansa@gmail.com \
--cc=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