From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/gutenprint: add back the hook for creating the m4local directory
Date: Tue, 18 Feb 2020 03:50:39 +0100 [thread overview]
Message-ID: <20200218035039.331cfa0f@windsurf> (raw)
In-Reply-To: <20200217225202.1640973-1-fontaine.fabrice@gmail.com>
On Mon, 17 Feb 2020 23:52:02 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Commit 64c42c5e2c26261e26c3548c86b02f55d12f341b removed the hook for
> creating the m4local directory with the assumption that it would be
> created because the first include is treated in a special way if it
> doesn't exists
>
> However, this assumption was wrong as m4local is the second include, the
> first one is m4 (which already exists in the archive). So put back the
> hook. The other solutions would be to patch:
> - Makefile.{am,in} to remove m4local
> - configure.ac and Makefile.{am,in} to add m4local before m4
> However, both solutions don't seem to be upstreamable
>
> Fixes:
> - http://autobuild.buildroot.org/results/e40313c6ec193d6156e26eff62303545fba09413
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/gutenprint/gutenprint.mk | 7 +++++++
> 1 file changed, 7 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-02-18 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 22:52 [Buildroot] [PATCH 1/1] package/gutenprint: add back the hook for creating the m4local directory Fabrice Fontaine
2020-02-18 2:50 ` Thomas Petazzoni [this message]
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=20200218035039.331cfa0f@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