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

Bug#220244: gtk-engines-gtkstep_2.2-1.2(mipsel/unstable): configure built with broken libtool.m4

Package: gtk-engines-gtkstep
Version: 2.2-1.2
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of gtk-engines-gtkstep_2.2-1.2 on repeat.rfc822.org by sbuild/mipsel 1.170.4
> Build started at 20031029-0809

The version of libtool used to build this source package is too old to
correctly support shared libraries for the Debian mips and mipsel
architectures.  Debian versions 1.5-2 and 1.4.2-7 and higher correctly
support them.  You need to update all of the libtool related files by
running the following on your source tree:

	autoreconf --force

You may need to use the --install option as well.  You can also try the
individual commands needed yourself:

	libtoolize --force --copy
	automake -a

autoheader may not be needed, and you may need to use versioned binaries
(autoconf2.13, automake-1.{4,6,7}, aclocal-1.{4,6,7}, etc)

The correct 'configure' script will have output that looks like this:
# This must be Linux ELF.
  case $host_cpu in
  alpha* | hppa* | i*86 | mips | mipsel | powerpc* | sparc* | ia64* | arm* | m68k)
    lt_cv_deplibs_check_method=pass_all ;;

It is important that mips and mipsel (or mips*), arm, and m68k are
listed in the configure script here, or seeing the following comment:
  # linux always uses pass_all now, this code is the old way (tm)

Older versions of libtool used a file_magic check for the pattern
file_magic ELF [0-9][0-9]*-bit [LM]SB (shared object|dynamic lib )

The output of file(1) on a shared library on MIPS does not match this
regular expression, however.  Earlier versions of file had been
modified to match this regular expression, but the latest version uses
the same output as upstream once again.  The file check often causes
problems, and results on a build-dep on file that you might not
otherwise be aware of.  The new method doesn't need file(1) at all,
and is far less fragile, so it is best to upgrade the configure script
with proper mips support.

Reply to: