Description of problem: I've got: ``` running: aclocal running: autoheader running: automake -a Use of uninitialized value $macro in exists at /usr/bin/automake line 5268, <GEN0> line 1. Use of uninitialized value $macro in concatenation (.) or string at /usr/bin/automake line 5268, <GEN0> line 1. automake: error: unrequested trace '' automake: Please contact <bug-automake <at> gnu.org>. at /usr/share/automake-1.16/Automake/Channels.pm line 662, <GEN0> line 1. Automake::Channels::msg("automake", "", "unrequested trace ''") called at /usr/share/automake-1.16/Automake/ChannelDefs.pm line 212 Automake::ChannelDefs::prog_error("unrequested trace ''") called at /usr/bin/automake line 5268 Automake::scan_autoconf_traces("configure.ac") called at /usr/bin/automake line 5527 Automake::scan_autoconf_files() called at /usr/bin/automake line 8355 ``` [As you can also see in my CI log: https://github.com/pmem/pmemkv/runs/1483659444?check_suite_focus=true#step:4:2002 ] Version-Release number of selected component (if applicable): Fedora Rawhide (build in docker) autoconf noarch 2.69-34.fc33 automake noarch 1.16.2-3.fc34 How reproducible: Always Steps to Reproduce: ``` git clone https://github.com/pmem/valgrind.git (but tested also with non-forked, original repo: git clone git://sourceware.org/git/valgrind.git) cd valgrind ./autogen.sh ``` [this is a test step of my CI: https://github.com/pmem/pmemkv/blob/master/utils/docker/images/install-valgrind.sh#L31 ] Additional info: I've reported a bug to automake support and they couldn't reproduce this bug on the clean version (not from any distro): https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44992#8 It does not fail on stable Fedora releases (32 & 33).
As Fedora Rawhide is not to be considered a stable release, this is not a high priority issue at the moment. However, we surely need to address this before the release of Fedora 34, so thank you for the report. I will post any updates here as soon as I can get to it.
Are you able to reproduce this issue now (on updated Fedora Rawhide)? I'm not getting the error anymore. ``` $ ./autogen.sh running: aclocal running: autoheader running: automake -a configure.ac:30: installing './compile' configure.ac:201: installing './config.guess' configure.ac:201: installing './config.sub' configure.ac:14: installing './install-sh' configure.ac:14: installing './missing' Makefile.vex.am: installing './depcomp' running: autoconf ```
As previously, I used fedora rawhdie in docker. I got the latest docker I could find. I run: # docker pull registry.fedoraproject.org/fedora:rawhide inside the container I only installed needed tools: # dnf install git autoconf automake and I successfully reproduced the issue (using my original steps). I'm not sure what is the exact version of Fedora (`docker images` command says it was "Created 4 days ago").
I've tested inside a container after a fresh pull from registry.fedoraproject.org/fedora:rawhide. With only 'git', 'autoconf' and 'automake' installed, the install-valgrind.sh script you've referenced in the original post, exits due to a compiler not being present, but after a successful clone, checkout and ./autogen.sh run. I'm also able to run ./autogen.sh manually without any errors. With valgrind build dependencies installed, the script exits correctly after a successful build of valgrind. Since I'm unable to reproduce the issue, I'm closing this report now. Please, check your configuration and if you find any additional information which could help to reproduce the issue, feel free to re-open this report.
Created attachment 1754813 [details] cmake success /Zc:cplusplus flag
Sorry, I've uploaded the attachment by mistake. Anyway, I'm not sure how crazy that would be, but I seem to find a pattern where it can be reproduced. I'm using Ubuntu as a host for the docker, as is our CI. I believe you used Fedora as a host, and so did my colleague which also could not reproduce my issue. I'm not saying you should follow on this clue, but perhaps it will give someone some idea how this could affect this issue.