When you run autoconf/automake (from ports at least), they usually say that you should export variables like AUTOCONF_VERSION and AUTOMAKE_VERSION to something like 2.11 or 1.9 or so.
For me: $ pkg_info | grep auto autoconf-2.59p3 automatically configure source code on many Un*x platforms autoconf-2.69p0 automatically configure source code on many Un*x platforms automake-1.12.6 GNU Standards-compliant Makefile generator automake-1.13.1 GNU Standards-compliant Makefile generator automake-1.9.6p10 GNU Standards-compliant Makefile generator it would be AUTOCONF_VERSION=2.59 or =2.69 and AUTOMAKE_VERSION=1.12, =1.13 and so on. If you have gotten auto* installed by yourself and not via ports, then reading the output/log from the autosetup would be in order. 2013/8/29 Richard Thornton <thornton.rich...@gmail.com> > My Sun Blade 100, has a fresh install of 5.3, and its very good, much > better than 5.1; XFCE is very stable and R is much better than prior > ports. you guys did a great job! Now this computer sits running actively, > with nothing to do! So lets run Seti on it, but alas, no recent binary for > OpenBSD Sparc64 seems to be found. Thus I tried last night to compile my > own, but the _autosetup script fails saying it can't find > M4 >= 1.4 (not true, I have latest), automake( not true I have latest), > autoconf (not true I have latest). The only thing it finds is gmake, which > passes. Is there some sort of special tailoring necessary for OpenBSD? Or > has someone solved all these issues already and could help me out? Thanks, > Richard. > > -- May the most significant bit of your life be positive.
