Build Error for v1.3

[patroclos]

Build Error for v1.3

[patroclos]

This is quite strange, as nothing changed about the configure.ac script.
Did you run autoreconf -i?

[Vaelatern]

Yes. Really unsure as to what is wrong here.

[Vaelatern]

My version:
autoreconf (GNU Autoconf) 2.69

[patroclos]

Well, thats even stranger, as I have the same version

[Vaelatern]

Same issue for autoreconf -fi and autoreconf -i

[patroclos]

I think the latest commit should fix things for you, since your problem only seems to be with the arguments

[Vaelatern]

When I apply your latest commit, d102ab2, I get a similar error:

checking for a BSD-compatible install... /builddir/.xbps-PAmix/wrappers/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
./configure: line 2903: syntax error near unexpected token `ac_ext=cpp'
./configure: line 2903: `ac_ext=cpp'

Which is 3 lines after AX_CXX_COMPILE_STDCXX_11() is present in the configure script. I don't know if that is intentional.

[Vaelatern]

My autotools complains when I change the patch:

./configure: line 2900: syntax error near unexpected token `11'
./configure: line 2900: `AX_CXX_COMPILE_STDCXX(11)'

From reading the docs it seems this should not be an issue.
Perhaps some m4 settings need tuning?

[patroclos]

I think you may be required to surround the arguments in rectangular brackets
for example: AX_CXX_COMPILE_STDCXX([11], [noext], [mandatory])

[Vaelatern]

This was after I did so.

[patroclos]

so did you change something regarding autoconf and/or was the configure script working for you prior to 1.3?

[Vaelatern]

In 1.2 only a makefile was used. Basically, both of these invocations failed: AX_CXX_COMPILE_STDCXX([11])
AX_CXX_COMPILE_STDCXX(11)

[patroclos]

Oh, I was assuming you were on the master branch.
I was able to reproduce your issue, you need to install autoconf-archive and reconfigure

[Vaelatern]

Excellent! Thank you!

[Cheaterman]

Thanks for the simple answer, I ran into this today - this is a relatively uptodate Gentoo, probably the autoconf-archive package is simply missing from the current ebuild dependencies. :-)

[patroclos]

@Cheaterman Thats strange, autoconf-archive should be in ebuild dependencies since this bug

[Cheaterman]

@patroclos Thanks a lot for your answer and interest! I can confirm that my other computers' Portage trees all include ebuilds that properly depend on sys-devel/autoconf-archive, so I guess my Portage tree on that machine was much more outdated than I expected. Sorry for the bump everyone, my bad!