[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: help needed with mips build failure



Steve Langasek <vorlon@debian.org> writes:

> You're using an old (and broken) version of libtool.  C.f.
> <http://lists.debian.org/debian-qa-packages/2003/09/msg00023.html> for
> Ryan's boilerplate explanation for fixing this problem.

Thanks a bunch, this is surely the problem, but applying the solution
is causing problems.  autoreconf --force blows chunks.

Now, it should be noted, upstream uses autoconf 2.13, and libtool
1.4c.  So these errors should not be happening, and seem to imply
problems in the Debian auto* packages.

First, from automake, errors referring to all the Makefile.am's in the
package, complaining that variable such as GNOME_LIBDIR, GNOMEUI_LIBS,
GUILE_LIBS, and so forth, are all not defined.  It should be noted
that gnucash uses gnome version 1, so if the "compatibility" automake
2.13 stuff (which gnucash also needs) does not still correctly support
the relevant macros, we're in trouble.

Then I get the oh-so-pleasing error messages from autoconf:

  autoconf: Undefined macros:
  ***BUG in Autoconf--please report*** AC_HELP_STRING
  ***BUG in Autoconf--please report*** AC_HELP_STRING
  ***BUG in Autoconf--please report*** AC_CONFIG_COMMANDS
  ***BUG in Autoconf--please report*** AC_COMPUTE_INT
  ***BUG in Autoconf--please report*** AC_COMPUTE_INT
  ***BUG in Autoconf--please report*** AC_COMPUTE_INT

followed by complaints about the way AC_TRY_RUN is being called.

Then the truly weird stuff from autoheader, such as:

  /usr/bin/autoheader2.13: line 243: _snprintf, and to 0 if you dont.: command not found

(never mind that line 243 of autoheader2.13 contains only whitespace)

The same errors occur if I run the commands individually instead of
using autoreconf.

Thomas



Reply to: