autoreconf from autoconf-2.70 creates broken configure script #3491
Labels
No labels
a=ActionBeforeRelease
a=Bugwash Today
a=Implement
a=Move To VIP
a=NextVCL
a=OK'ed
a=RunByUPLEX
a=VDD
a=duplicate
a=feedback please
a=freeze
a=help wanted
a=invalid
a=last call
a=more-info-needed
a=need bugwash
b=breaking
b=bug
b=cleanup
b=enhancement
c=H/2
c=build
c=doc
c=packaging
c=varnishadm
c=varnishapi
c=varnishd
c=varnishhist
c=varnishlog
c=varnishncsa
c=varnishstat
c=varnishtest
c=varnishtop
c=vmod
r=6.0
r=7.0
r=7.1
r=7.2
r=7.3
r=7.4
r=7.5
r=8.0
r=trunk
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
vinyl-cache/vinyl-cache#3491
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This has initially been reported downstream at Gentoo: https://bugs.gentoo.org/751190
BUT this was with a autoconf-2.70-beta version. The error message with autoconf-2.70-final has changed but the outcome has not. The
configurescript created by autoreconf from autoconf-2.70 is broken and fails to finish:I've tried to attach the config.log file to this issue but GitHub won't let me. So I've uploaded the config.log file to my personal web space: https://www.gentoofan.org/gentoo/misc/varnish-6.5.1-config.log
my rough guess would be an issue with the
AC_PROG_INSTALLmacro. Can you also make available the generatedconfigurescript?Sure. Here it is: https://www.gentoofan.org/gentoo/misc/varnish-6.5.1-configure
This looks clearly broken:
# <== hereaddedI do not think we can do anything about it, but would like to ask @Dridi to have a second look.
I can recreate it on arch, it works in
autoconf-2.69but not inautoconf-2.70https://www.winehq.org/pipermail/wine-devel/2020-October/176324.html describes the problem and :
seems to solve it.
@gquintard adding arch to cci should be right around you alley, do we want that?
happy to do it
done
I actually went a bit further, the
distcheckjobs nowmake distcheckdirectly from thegitcheckout to catch these issues.