[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Making Autoconf 2.70 happen in the near future
From: |
Michael Orlitzky |
Subject: |
Re: Making Autoconf 2.70 happen in the near future |
Date: |
Tue, 10 Mar 2020 12:50:53 -0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 |
On 3/10/20 11:28 AM, Zack Weinberg wrote:
>
> Thanks for the suggestion! I have no experience with Gentoo myself
> but I've made a note to look at doing this at some point. You say you
> automatically regenerate the configure script for any package that
> needs to patch the build system, but do you have a way to direct a
> bootstrap cycle to *unconditionally* regenerate the configure scripts
> for each package?
Not out-of-the-box, but our packages are essentially bash scripts, so it
should be pretty easy to hack the package manager to insert a line or
two that rebuilds everything whenever e.g. configure.{in,ac} is present.
As a proof-of-concept, adding
pre_src_prepare() {
[[ -f configure.ac || -f configure.in ]] && autoreconf -fi
}
to /etc/portage/bashrc [0] seems to work in the few simple cases I tried.
[0] https://wiki.gentoo.org/wiki//etc/portage/bashrc
- Making Autoconf 2.70 happen in the near future, Zack Weinberg, 2020/03/09
- Re: Making Autoconf 2.70 happen in the near future, Nicholas Clark, 2020/03/09
- Re: Making Autoconf 2.70 happen in the near future, Bob Friesenhahn, 2020/03/09
- Re: Making Autoconf 2.70 happen in the near future, Per Bothner, 2020/03/09
- Re: Making Autoconf 2.70 happen in the near future, Michael Orlitzky, 2020/03/09
- Re: Making Autoconf 2.70 happen in the near future, Werner LEMBERG, 2020/03/10
- Re: Making Autoconf 2.70 happen in the near future, Zack Weinberg, 2020/03/23
- Re: Making Autoconf 2.70 happen in the near future, Marko Lindqvist, 2020/03/24