[Top][All Lists]

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

libtool-2.2.11a on AIX 5.3 current git master / followup on the old test

From: Rainer Tammer
Subject: libtool-2.2.11a on AIX 5.3 current git master / followup on the old test suite and failures in the new testsuit
Date: Thu, 05 Aug 2010 09:25:14 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv: Gecko/20070326 Thunderbird/ Mnenhy/

 Hello Ralf,
I just refreshed my source from git and rerun the test suit on AIX 5.3.

I added the patch below to get reliable results from the old test suit.

> I'm still undecided on whether we should set that for the old testsuite,
> or go for the more general solution and just turn set o-rwx for *all*
> uninstalled libraries we generate on AIX, and only turn the bits on at
> `make install' time.  That way we would still require the umask in the
> testsuite, but developers of packages using libtool might be better off.
This part is still open. On a first look this approach looks not bad.
There is certainly no
big performance loss if the shared libraries are unloaded after
execution. Furthermore we
do not need to worry about slibclean.

# diff -c defs.m4sh /daten/source/libtool-2.2.11a/tests/defs.m4sh
*** defs.m4sh   Wed Aug  4 14:45:41 2010
--- /daten/source/libtool-2.2.11a/tests/defs.m4sh       Thu Aug  5
08:17:53 2010
*** 131,136 ****
--- 131,137 ----
+ host_os
  build_alias" "$LIBTOOL --config" ": fatal"

*** 350,355 ****
--- 351,365 ----
  scripts="$auxdir/ltmain.m4sh $srcdir/libtoolize.m4sh"
+ # On AIX, shared libraries remain loaded in memory after use if they
+ # are world-readable, until root issues slibclean.  On NFS, this causes
+ # a testsuite rerun to fail to clean up test group directories.  Avoid
+ # this with a suitable umask.  Do not do this on other systems, for
+ # example HP-UX suffers unless shared libraries are mode 555.
+ case $host_os in
+ aix*) umask o-rwx ;;
+ esac

  func_msg "Running $progname"


The new test suite still yields many failures in comparison to 2.2.8.

# grep FAILED check.log
 38: Link order of deplibs                           FAILED
 41: Runpath in libtool library files                FAILED
 53: bindir install tests                            FAILED (bindir.at:295)
 55: deplib in subdir                                FAILED
 64: versioning                                      FAILED
 66: DESTDIR with in-package deplibs                 FAILED (destdir.at:127)
 72: lt_dlopenadvise library loading                 FAILED
 75: lt_dlopenext error messages                     FAILED
 76: libdir of installed modules                     FAILED
 83: enforced lib prefix                             FAILED
 99: template test with subdirs                      FAILED
100: C++ static constructors                         FAILED (ctor.at:65)
101: C++ exception handling                          FAILED
104: AC_NO_EXECUTABLES                               FAILED
111: Run tests with low max_cmd_len                  FAILED
112: override pic_flag at configure time             FAILED (pic_flag.at:46)

## ------------- ##
## Test results. ##
## ------------- ##

ERROR: 105 tests were run,
18 failed (2 expected failures).
11 tests were skipped.
## -------------------------- ##
## testsuite.log was created. ##
## -------------------------- ##

Please send `tests/testsuite.log' and all information you think might help:

   To: <address@hidden>
   Subject: [GNU Libtool 2.2.11a] testsuite: 38 41 53 55 64 66 72 75 76
83 99 100 101 104 111 112 failed

I have added the test suite log to this post.

One question to test 053:

This is AIX, why do I see libraries in


Attachment: testsuite.log.gz
Description: GNU Zip compressed data

reply via email to

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