From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/bc: bump to 1.07.1
Date: Fri, 13 Sep 2019 19:46:22 +0200 [thread overview]
Message-ID: <20190913194622.303b5a31@windsurf.home> (raw)
In-Reply-To: <20190912205057.40777-1-matthew.weber@rockwellcollins.com>
Hello Matt,
On Thu, 12 Sep 2019 15:50:57 -0500
Matt Weber <matthew.weber@rockwellcollins.com> wrote:
> * Added license hash files
> * Updated site to new GNU location
> * Reconfig required to use newer automake
> * Dropped patch for 01_array_initialize.patch as it was fixed
> in the latest
> * Refactored patches for makeinfo variable and write io errs
> * Added new dc fix exit code patch from Debian sid
> * Added new libmath offline gen cross-compile patch from Yocto
>
> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
Do you know what is the upstream status for the different patches we
had and that are still needed ?
> diff --git a/package/bc/0001-bc-use-MAKEINFO-variable-for-docs.patch b/package/bc/0001-bc-use-MAKEINFO-variable-for-docs.patch
> new file mode 100644
> index 0000000000..6f82e9f82e
> --- /dev/null
> +++ b/package/bc/0001-bc-use-MAKEINFO-variable-for-docs.patch
> @@ -0,0 +1,34 @@
> +From 66d30778ec5bf98dbd106a3287d17fe0b5123490 Mon Sep 17 00:00:00 2001
> +From: Matt Weber <matthew.weber@rockwellcollins.com>
> +Date: Wed, 11 Sep 2019 21:57:35 -0500
> +Subject: [PATCH] bc: use MAKEINFO variable for docs
> +
> +Use the appropiate MAKEINFO variable rather than the hardcoded makeinfo
> +command directly, otherwise missing logic never works.
> +
> +Fixes:
> +http://autobuild.buildroot.net/results/b0b/b0b9dced0014a5a8026fa972f95085e8bd16a07b/
> +
> +[Recreated for 1.0.7.1 by Matt W]
> +Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> +Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
> +---
> + doc/Makefile.in | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
This patch is useless, because it modifies Makefile.in, but you have
AUTORECONF = YES, so Makefile.in will be regenerated from Makefile.am.
> +[Reformatted to GIT for 1.0.7.1 by Matt W]
> +Signed-off-by: Ross Burton <ross.burton@intel.com>
> +Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
> +---
> + bc/Makefile.am | 8 --------
You're modifying Makefile.am here.
> +# Need to reconf to fix automake-1.14: command not found
> +BC_AUTORECONF = YES
And so the reason for the autoreconf = yes is not "automake: command
not found", it's because you're patching Makefile.am, so it is newer
than the corresponding Makefile.in, and consequently, the autotools
machinery tries to regenerate it by calling automake. So the comment
here should be the usual:
# We're patching Makefile.am
or, the file name of the patch touching Makefile.am.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-13 17:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 20:50 [Buildroot] [PATCH] package/bc: bump to 1.07.1 Matt Weber
2019-09-13 17:46 ` Thomas Petazzoni [this message]
2019-09-13 18:14 ` Matthew Weber
2019-09-13 18:31 ` Thomas Petazzoni
2019-09-13 18:34 ` Thomas Petazzoni
2019-09-13 18:40 ` [Buildroot] [External] " Matthew Weber
2019-09-13 19:53 ` Thomas Petazzoni
2019-09-13 18:34 ` [Buildroot] " Matthew Weber
2019-09-13 18:37 ` Thomas Petazzoni
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=20190913194622.303b5a31@windsurf.home \
--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