From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to force AUTORECONF for everything
Date: Thu, 16 Feb 2017 22:20:26 +0100 [thread overview]
Message-ID: <20170216222026.788ee7b3@free-electrons.com> (raw)
In-Reply-To: <20170216174538.GC4986@free.fr>
Hello,
On Thu, 16 Feb 2017 18:45:38 +0100, Yann E. MORIN wrote:
> No, there is no global setting that forces that behaviour.
>
> You'll have to hack the autotools infra. See in package/pkg-autotools.mk at 143:
>
> 139 ifndef $(2)_AUTORECONF
> 140 ifdef $(3)_AUTORECONF
> 141 $(2)_AUTORECONF = $$($(3)_AUTORECONF)
> 142 else
> 143 $(2)_AUTORECONF ?= NO
> 144 endif
> 145 endif
>
> You may want to change that "NO" to a "YES"
>
> But beware, here be dragins...
In theory, there should be no dragons.
In practice, lots and lots of package to not autoreconf properly, so
you're going to face a *lot* of build failures by forcing autoreconf on
all packages.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-02-16 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 17:11 [Buildroot] How to force AUTORECONF for everything Sidney Manning
2017-02-16 17:45 ` Yann E. MORIN
2017-02-16 21:20 ` 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=20170216222026.788ee7b3@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox