From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tslib: speed up the build by skipping autoreconf
Date: Thu, 27 Apr 2017 11:30:14 +0200 [thread overview]
Message-ID: <87k266kxjt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1493284513-7365-1-git-send-email-martin.kepplinger@ginzinger.com> (Martin Kepplinger's message of "Thu, 27 Apr 2017 11:15:13 +0200")
>>>>> "Martin" == Martin Kepplinger <martin.kepplinger@ginzinger.com> writes:
> Signed-off-by: Martin Kepplinger <martin.kepplinger@ginzinger.com>
> ---
> hi,
> this is more of a question what buildroot's stand is on this. Can there be
> benefit from doing autoreconf in a real tarball release? In case there is
> no patch against the relevant build sources, I guess not, but you'll know
> better.
Committed, thanks.
In Buildroot we only do autoreconf if it is needed, E.G. if we have a
patch modifying one of the auto* files (configure.ac, Makefile.am,
..). Apparently the AUTORECONF = YES line was not removed from tslib.mk
when such patches were removed in a version bump.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-04-27 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 9:15 [Buildroot] [PATCH] tslib: speed up the build by skipping autoreconf Martin Kepplinger
2017-04-27 9:30 ` Peter Korsgaard [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=87k266kxjt.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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