libtool
[Top][All Lists]
Advanced

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

libtool pre-1.5b tests fail on 9 debian arches


From: Robert Millan
Subject: libtool pre-1.5b tests fail on 9 debian arches
Date: Fri, 26 Sep 2003 19:46:31 +0000
User-agent: Mutt/1.5.4i

[ CCing to debian maintainer and libtool upstream ]

Hi there folks.

The libtool upstream maintainers are preparing a new 1.5b release. On their
behalf I've recently attempted to test a snapshot from CVS branch-1-5 on all
architectures Debian supports (or pretends to support) that I had access to.

The results (below) are unfavorable on at least 4 arches, and undetermined on
5 more arches. For any arch that is not marked "ok" below, someone should
_urgently_ test and/or fix it before libtool 1.5b is released. For those of
you unaware of the insanely detrimental consequences a brokenly released
libtool can have for your port, see footnote [5].

For testing libtool branch-1-5, get a CVS snapshot while passing
"-r branch-1-5" to the checkout command, and run:

  export CVSROOT=:pserver:address@hidden:/cvsroot/libtool
  cvs -z9 co -r branch-1-5 libtool ; cd libtool
  ./bootstrap && ./configure && make && make check

------------------------
host - cpu - test result
------------------------

gluck           i386    ok
voltaire        powerpc ok
merulo          ia64    17 tests failed
casals          mips    ?? [3]
debussy         arm     ok
escher          alpha   ok
raptor          s390    3 tests failed
paer            hppa    4 tests failed
crest           m68k    ?? [3]
vore            sparc   ?? [3]
ravel [1]       amd64   25 tests failed
williams        mipsel  ?? [2]
??              sh      ?? [4]

[1] access by request, see w.d.o/ports/amd64/
[2] williams and vaughan are down
[3] test fails due to host-related autotools/texinfo/etc stuff
[4] no publicly known developer machine available

[5] libtool's released code spreads itself to projects using libtool in a way
much similar to autoconf or automake. If a libtool release is broken for a
particular arch, then all packages that get their libtool updated in upstream
will start to fail for that arch, and need individual patching. This is what
recently happened to the mips port.

-- 
Robert Millan

"[..] but the delight and pride of Aule is in the deed of making, and in the
thing made, and neither in possession nor in his own mastery; wherefore he
gives and hoards not, and is free from care, passing ever on to some new work."

 -- J.R.R.T, Ainulindale (Silmarillion)

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]