t;release"?
I'm more likely to build from a git clone. And I believe best practice
is to not include autotools-generated scripts in the repository,
but instead add 'autoreconfig -i' as an initial first step.
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
Windows with WSL (i.e. Ubuntu) and Mac with HomeBrew fairly easily.
I can probably test plain Windows (without WSL), but I know less about which
compilers to install etc, so that would probably be more work, though
I need to deal with plain Windows at some point for other reasons.
--
--Per
m tests conditionally: depend conditionally
on their output!" doesn't apply when the tests conditionally abort ...
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
___
Autoconf mailing list
Autoconf@gnu.org
https://lists.gnu.org/mailman/listinfo/autoconf
Akim Demaille wrote:
>>>>>>"Per" == Per Bothner <[EMAIL PROTECTED]> writes:
> Per> Unfortuntely, autoconf 2.52 does not define 'Java' as a language.
> Per> But that can probably be worked around.
>
> Autoconf 2.52+ would be most ha
ertainly *looks* wrong to set dirpart to "", considering
the mkdir "$dirpart/$DEPDIR" just below.
--
--Per Bothner
[EMAIL PROTECTED] http://www.bothner.com/per/
Index: aclocal.m4
===
RCS file: /cvsroot/aut
l have plenty of options:
(a) Stick to an old (legacy) verison of gcc, which I suspect is what most
legacy users are going to do.
(b) Install bash on the machine they use to compile gcc.
(c) Cross-compile gcc on some other system.
People who are using 4.3BSD *and* want to install a new gcc compil
