From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] freetype: drop calling autogen, no longer needed
Date: Thu, 11 Oct 2018 17:13:24 +0200 [thread overview]
Message-ID: <20181011171324.22c3ec20@windsurf> (raw)
In-Reply-To: <20181003134001.23537-1-thomas.petazzoni@bootlin.com>
Hello,
On Wed, 3 Oct 2018 15:40:01 +0200, Thomas Petazzoni wrote:
> In commit a31a66802a7a1af76a629b0ba7120424ed547646 ("freetype:
> security bump to version 2.5.3"), the freetype package was changed to
> call ./autogen.sh to regenerate the autotools stuff, because the
> ltmain.sh provided by upstream freetype was not compatible with
> Buildroot libtool-patching logic.
>
> Since then, freetype has been bumped several times, and the current
> version packaged in Buildroot has an ltmain.sh that is compatible with
> our libtool-patching logic.
>
> Therefore, this commit drops the no longer needed autogen stuff.
>
> This autogen stuff was badly breaking per-package host/target
> directory, because the autogen happened at the post-patch hook step,
> at which point the host-automake/host-autoconf/host-libtool
> dependencies have not yet been copied into this package host
> directory.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> package/freetype/freetype.mk | 18 ------------------
> 1 file changed, 18 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-11 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 13:40 [Buildroot] [PATCH] freetype: drop calling autogen, no longer needed Thomas Petazzoni
2018-10-11 15:13 ` Thomas Petazzoni [this message]
2018-10-24 10:40 ` Peter Korsgaard
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=20181011171324.22c3ec20@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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