Autoconf 2.72 seems to be under preparation upstream, I therefore started to build dependent components to verify that they can be built once it lands in Fedora. Your component fails to build with the new version of autoconf, due to the following error: --- checking for __clear_cache... yes ./configure: line 21740: syntax error near unexpected token `;;' ./configure: line 21740: ` '' ;;' error: Bad exit status from /var/tmp/rpm-tmp.LOSgoc (%build) Bad exit status from /var/tmp/rpm-tmp.LOSgoc (%build) RPM build errors: Child return code was: 1 --- From further investigation, and after discussion with autoconf mailing list, it looks like there is a quoting error in the aclocal.m4{,.cross} files. The proposed patch is as follows, which modifies the quoting and replaces the call of AC_EGREP_CPP by a call of AC_PREPROC_IFELSE, which is sipler and more efficient.: --- diff -U5 -r wine-7.20.old/aclocal.m4 wine-7.20/aclocal.m4 --- wine-7.20.old/aclocal.m4 2022-11-17 17:19:01.772386752 +0100 +++ wine-7.20/aclocal.m4 2022-11-17 17:24:03.721683055 +0100 @@ -279,15 +279,17 @@ dnl dnl Usage: WINE_CHECK_DEFINE(name),[action-if-yes,[action-if-no]]) dnl AC_DEFUN([WINE_CHECK_DEFINE], [AS_VAR_PUSHDEF([ac_var],[ac_cv_cpp_def_$1])dnl -AC_CACHE_CHECK([whether we need to define $1],ac_var, - AC_EGREP_CPP(yes,[#ifndef $1 -yes -#endif], - [AS_VAR_SET(ac_var,yes)],[AS_VAR_SET(ac_var,no)])) +AC_CACHE_CHECK([whether we need to define $1], ac_var, + [AC_PREPROC_IFELSE([[ +#ifndef $1 +#error not defined +#endif +]], + [AS_VAR_SET(ac_var,yes)],[AS_VAR_SET(ac_var,no)])]) AS_VAR_IF([ac_var],[yes], [CFLAGS="$CFLAGS -D$1" LINTFLAGS="$LINTFLAGS -D$1"])dnl AS_VAR_POPDEF([ac_var])]) diff -U5 -r wine-7.20.old/aclocal.m4.cross wine-7.20/aclocal.m4.cross --- wine-7.20.old/aclocal.m4.cross 2022-11-17 17:19:01.035390916 +0100 +++ wine-7.20/aclocal.m4.cross 2022-11-17 17:24:49.854420729 +0100 @@ -277,14 +277,16 @@ dnl Usage: WINE_CHECK_DEFINE(name),[action-if-yes,[action-if-no]]) dnl AC_DEFUN([WINE_CHECK_DEFINE], [AS_VAR_PUSHDEF([ac_var],[ac_cv_cpp_def_$1])dnl AC_CACHE_CHECK([whether we need to define $1],ac_var, - AC_EGREP_CPP(yes,[#ifndef $1 -yes -#endif], - [AS_VAR_SET(ac_var,yes)],[AS_VAR_SET(ac_var,no)])) + [AC_PREPROC_IFELSE([[ +#ifndef $1 +#error not defined +#endif +]], + [AS_VAR_SET(ac_var,yes)],[AS_VAR_SET(ac_var,no)])]) AS_VAR_IF([ac_var],[yes], [CFLAGS="$CFLAGS -D$1" LINTFLAGS="$LINTFLAGS -D$1"])dnl AS_VAR_POPDEF([ac_var])]) --- Please review, and feedback if you have any concern.
Please note, there may be a mistake in the proposed patch: + [AS_VAR_SET(ac_var,yes)],[AS_VAR_SET(ac_var,no)])]) Should probably be + [AS_VAR_SET(ac_var,no)],[AS_VAR_SET(ac_var,yes)])])
Thanks. Have you submitted this upstream?
(In reply to Michael Cronenworth from comment #2) > Thanks. Have you submitted this upstream? No sorry, I'm afraid I have enough to deal with regarding this autoconf 2.72 update :) I leave the follow up to you.
FEDORA-2022-d92e5f5f03 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d92e5f5f03
FEDORA-2022-6520ef0a4b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6520ef0a4b
FEDORA-2022-d92e5f5f03 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-d92e5f5f03` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d92e5f5f03 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-6520ef0a4b has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-6520ef0a4b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6520ef0a4b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-6520ef0a4b has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-d92e5f5f03 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.