I'm working on Fedora 28, x86_64 (fully patched). I suppose the CFLAGS
of "-DNDEBUG -g2 -O2 -m64 -march=native" are causing the warnings.
gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include -DNDEBUG -g2 -O2
-m64 -march=native -fPIC -MT glob.o -MD -MP -MF .deps/glob.Tpo -c -o
glob.o glob.c
mv -f
$ autoreconf -f -i
configure.ac:35: error: require Automake 1.16.1, but have 1.15.1
autoreconf: automake failed with exit status: 1
Please consider dropping version requirements. I'm working on Fedora
28. Fedora is know for having some of the most up to date tools.
If something can't build on
On Fri, 2018-08-24 at 19:46 -0400, Jeffrey Walton wrote:
> $ autoreconf -f -i
> configure.ac:35: error: require Automake 1.16.1, but have 1.15.1
> autoreconf: automake failed with exit status: 1
>
> Please consider dropping version requirements. I'm working on Fedora
> 28. Fedora is know for
> I *thought* we are supposed to avoid alloca in 2018.
Amen brother.
martind@swiftboat:~/download/make-git/src$ sgrep -w alloca | wc -l
115
martind@swiftboat:~/download/make-git/src$
Ugh.
> I'm building 4.2.1 from the tarball.
You'd have more luck from git, per:
On Fri, Aug 24, 2018 at 5:33 PM, Martin Dorey
wrote:
> I think that's essentially the same issue as the failed compile one. The
> bug I linked to there links to a mail thread that links to this mail thread:
>
> http://gnu-make.2324884.n4.nabble.com/undefined-reference-to-alloca-td18308.html
>
>
I'm working on Fedora 28, x86_64 (fully patched). I'm building 4.2.1
from the tarball.
I *thought* we are supposed to avoid alloca in 2018. I guess this is
another reason why.
--
...
gcc -DLOCALEDIR=\"/usr/local/share/locale\"
-DLIBDIR=\"/usr/local/lib64\"
I did warn you.
> Fedora is know for having some of the most up to date tools.
It must indeed be a cold day in hell, as I used automake 1.16.1 from Debian
Buster.
> there's no hope it can build where a newer GNU Make is truly needed
Perhaps the widespread lack of this automake is what's
