From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] augeas: bump to version 1.9.0
Date: Fri, 12 Jan 2018 22:35:01 +0100 [thread overview]
Message-ID: <20180112223501.396a6dc9@windsurf.lan> (raw)
In-Reply-To: <20180109201846.1156-1-joerg.krause@embedded.rocks>
Hello,
On Tue, 9 Jan 2018 21:18:46 +0100, J?rg Krause wrote:
> Add two patches from upstream to fix a build issue when building an
> example. Ideally, the examples should not be build at all. However,
> upstream disliked the idea of adding configure options like
> `--disable-examples` [1]. So we'll make do with the patches and force a
> autoreconf.
Well, since the patches are upstream, once a new release is made, we
can drop the patches, and remove AUTORECONF = YES, correct ?
> diff --git a/package/augeas/0001-examples-Makefile-fix-missing-trailing-backslash-for-dump-LDADD.patch b/package/augeas/0001-examples-Makefile-fix-missing-trailing-backslash-for-dump-LDADD.patch
> new file mode 100644
> index 0000000000..8ccd6b54b7
> --- /dev/null
> +++ b/package/augeas/0001-examples-Makefile-fix-missing-trailing-backslash-for-dump-LDADD.patch
> @@ -0,0 +1,21 @@
> +From d506cf6c1567cbb0a762c04d9354ab1694a5ac05 Mon Sep 17 00:00:00 2001
> +From: =?UTF-8?q?J=C3=B6rg=20Krause?= <joerg.krause@embedded.rocks>
> +Date: Mon, 11 Dec 2017 23:33:08 +0100
> +Subject: [PATCH] Update Makefile.am
> +
> +Add missing trailing backslash for `dump_LDADD`.
Missing SoB here and for the other patch as well. Could you fix this
and resend ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-12 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 20:18 [Buildroot] [PATCH] augeas: bump to version 1.9.0 Jörg Krause
2018-01-12 21:35 ` Thomas Petazzoni [this message]
2018-01-14 16:27 ` Jörg Krause
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=20180112223501.396a6dc9@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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 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.