Am 24.07.2005 um 23:52 schrieb Marc Espie:

If you care to investigate, you'll notice quite a few commits to OpenBSD m4 since OpenBSD 3.5. And guess what ? most of them have been to fix autoconf
behavior. And guess what ? the ports tree tracks OpenBSD-current, not
OpenBSD 2.0...

What you've done here is send people on a red herring's chase. I spent some time looking at that automake port, and figuring out why tests were wrong. Luckily, I noticed the gnumake checks, instead of embarking on autoconf
tests.

Well, Guile's autogen.sh still fails with the same error message that I got a couple of months ago when /usr/bin/m4 from OpenBSD-current is used:

automake-1.9: ####################
automake-1.9: ## Internal Error ##
automake-1.9: ####################
automake-1.9: unrequested trace `include'
automake-1.9: Please contact <bug-automake@gnu.org>.
at /usr/local/share/automake-1.9/Automake/Channels.pm line 562
Automake::Channels::msg('automake', '', 'unrequested trace `include\'') called at /usr/local/share/automake-1.9/Automake/ ChannelDefs.pm line 191 Automake::ChannelDefs::prog_error('unrequested trace `include \'') called at /usr/local/bin/automake-1.9 line 4675 Automake::scan_autoconf_traces('configure.in') called at / usr/local/bin/automake-1.9 line 4874 Automake::scan_autoconf_files() called at /usr/local/bin/ automake-1.9 line 7475
autoreconf-2.59: automake failed with exit status: 255

Guile's autogen.sh works when autoconf 2.59 is built with GNU m4.

OpenBSD improves all the time. You've actually stumbled on some of the
areas where problems have already been fixed.

It seems that there's still room for improvement ;-)

I've attached the autoconf and automake ports that I use.

Attachment: autotools-port.tar.gz
Description: GNU Zip compressed data

Reply via email to