Version 3.39-1 of the file utility changed the format of the output line for MIPS shared libraries again.
Older versions of libtool.m4 use the file utility and a regular expression to determine if something is a shared library or not. This regular expression does not match the new file output format. Newer versions of libtool instead use a much better checking method, however the following source packages have not updated (list obtained by grepping mips and mipsel build logs for the warning). a2ps ace-of-penguins bombermaze console-tools cronosii cyrus-sasl-nonus eeyes exult gacc gasql gimp-python gnome-admin gnome-objc gphoto greg gstalker gtk-engines gtk-engines-begtk gtranscript hermes1 infinity insight libgtrans-ifase libgtrans-mysql-3-23 libibtk libical libjpeg6b libopenobex libunicode lprng ltt mad mnogosearch mpqc mysql++ ngrep ntop nurbs++ open-amulet recode roxen rumba-manifold snac tdb tetex-bin tetradraw tex-guy tuxtime usbutils vdkbuilder vflib3 xalf xmlrpc-c xmms-cdread xmms-nas This means that on the mips and mipsel architectures the following warning is produced during configure. *** Warning: the command libtool uses to detect shared libraries, *** /usr/bin/file, produces output that libtool cannot recognize. *** The result is that libtool may fail to recognize shared libraries *** as such. This will affect the creation of libtool libraries that *** depend on shared libraries, but programs linked with such libtool *** libraries will work regardless of this problem. Nevertheless, you *** may want to report the problem to your system manager and/or to *** [EMAIL PROTECTED] An updated libtool will produce the following message during configure output on mips (a good method of checking whether you've updated or not). checking how to recognise dependent libraries... pass_all ~~~~~~~~ In order to update your packages to the latest version of libtool, ensure that libtool_1.4.3-10 is installed on your system and run the following commands from the source directory. $ libtoolize -cf $ aclocal $ autoconf You should also remove any "libtool" or "ltconfig" file left lying around from a previous version of libtool. Failure to run *all three* means you'll end up with a funted version of libtool. Also make sure that you run them in any sub-directory which ALSO runs libtool ( find . -type f | grep -e ltconfig -e ltmain ) Scott -- Who is nervous about his first ever mass-bug
signature.asc
Description: This is a digitally signed message part