Hi Michael, Thanks for the feedback.
Please Cc: either bug-libt...@gnu.org, which will cause a bug to be filed in our BTS for any new thread, or libtool@gnu.org for non-bug queries... There are often people far more knowledgeable than I available to help you when it comes to systems I have no access to. Yes, as you discovered, starting with Libtool-2.4.3 GNU M4 is required by libtoolize, because we now dynamically run the configure.ac through it to reliably detect build characteristics (as opposed to earlier releases which grepped and sedded through aclocal.m4 and configure.ac looking for magic strings heuristically). I did mention that in the NEWS and the release notes for 2.4.3, but I agree that it would be more sensible to simply fail at configure time when a suitable M4 is not found. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) > On 1 Dec 2014, at 09:58, Michael Felt <aixto...@gmail.com> wrote: > > runs much better - maybe you should fail configure when gnu m4 is not > available - as the tests fail nearly 100% when gnu m4 is not there. > >> On Mon, Dec 1, 2014 at 10:54 AM, Michael Felt <aixto...@gmail.com> wrote: >> My memory was bad (probably I had gnu m4 installed on my old build system). >> >> Will install gnu m4 and test. >> >>> On Mon, Dec 1, 2014 at 10:52 AM, Michael Felt <aixto...@gmail.com> wrote: >>> more feedback - make check FAILS miserably... >>> root@x064:[/data/prj/gnu/libtool/libtool-2.4.4]make check >>> GEN public-submodule-commit >>> make check-recursive >>> make[1]: Entering directory `/data/prj/gnu/libtool/libtool-2.4.4' >>> Making check in . >>> make[2]: Entering directory `/data/prj/gnu/libtool/libtool-2.4.4' >>> make check-local >>> make[3]: Entering directory `/data/prj/gnu/libtool/libtool-2.4.4' >>> CC libltdl/loaders/libltdl_libltdlc_la-preopen.lo >>> CC libltdl/libltdl_libltdlc_la-lt__alloc.lo >>> CC libltdl/libltdl_libltdlc_la-lt_dlloader.lo >>> CC libltdl/libltdl_libltdlc_la-lt_error.lo >>> CC libltdl/libltdl_libltdlc_la-ltdl.lo >>> CC libltdl/libltdl_libltdlc_la-slist.lo >>> CCLD libltdl/libltdlc.la >>> ## ----------------------------- ## >>> ## GNU Libtool 2.4.4 test suite. ## >>> ## ----------------------------- ## >>> >>> Libtoolize operation. >>> >>> 1: libtoolize macro installation FAILED >>> (libtoolize.at:100) >>> 2: libtoolize macro directory mismatch error FAILED >>> (libtoolize.at:121) >>> 3: multiple AC_CONFIG_MACRO_DIRS invocation FAILED >>> (libtoolize.at:153) >>> 4: multiple AC_CONFIG_MACRO_DIRS directories FAILED >>> (libtoolize.at:180) >>> 5: libtoolize ACLOCAL_AMFLAGS extraction FAILED >>> (libtoolize.at:216) >>> 6: libtoolize macro serial update FAILED >>> (libtoolize.at:248) >>> 7: libtoolize config files serial update FAILED >>> (libtoolize.at:325) >>> 8: diagnose missing LT_CONFIG_LTDL_DIR FAILED >>> (libtoolize.at:437) >>> 9: copy ltdl.m4 with shared macro directory FAILED >>> (libtoolize.at:527) >>> 10: correctly parse LTDL_INIT from configure.ac FAILED >>> (libtoolize.at:539) >>> 11: diagnose missing LTDL_INIT invocation FAILED >>> (libtoolize.at:614) >>> 12: upgrading verbatim style aclocal.m4 expected failure >>> (libtoolize.at:647) >>> 13: verbatim aclocal.m4 w/o AC_CONFIG_MACRO_DIRS expected failure >>> (libtoolize.at:782) >>> 14: nonrecursive ltdl with AC_CONFIG_MACRO_DIRS FAILED >>> (libtoolize.at:939) >>> 15: subproject ltdl with unconventional layout FAILED >>> (libtoolize.at:1015) >>> 16: Subproject ltdl without GNU M4 FAILED >>> (libtoolize.at:1087) >>> 17: LIBTOOLIZE_OPTIONS FAILED >>> (libtoolize.at:1121) >>> 18: cleanup old installation FAILED >>> (libtoolize.at:1160) >>> >>> Basic libtool operation. >>> >>> 19: check help output ok >>> 20: diagnose no mode specified ok >>> 21: quote shell meta-characters in filenames ok >>> 22: transform source suffices ok >>> 23: check link mode operation ok >>> 24: check objectlist file operation ok >>> 25: test LT_SUPPORTED_TAG interface skipped >>> (libtool.at:219) >>> >>> Linking and loading. >>> >>> 26: link against a preloaded static library testsuite: WARNING: A >>> failure happened in a test group before any test could be >>> testsuite: WARNING: run. This means that test suite is improperly designed. >>> Please >>> testsuite: WARNING: report this failure to <bug-libt...@gnu.org>. >>> FAILED (demo.at:383) >>> >>> make check from 2.4.3 follows - that was not so bad if I recall. >>> >>>> On Mon, Dec 1, 2014 at 10:50 AM, Michael Felt <aixto...@gmail.com> wrote: >>>> Feedback - question about m4 - because it is in PATH... >>>> >>>> root@x064:[/data/prj/gnu/libtool/libtool-2.4.4]buildaix >>>> + CPPFLAGS="-I/opt/include" CFLAGS="-O2 -qlanglvl=extc99" ./configure \ >>>> --prefix=/opt \ >>>> --sysconfdir=/var/libtool/etc \ >>>> --sharedstatedir=/var/libtool/com \ >>>> --localstatedir=/var/libtool \ >>>> --mandir=/usr/share/man \ >>>> --infodir=/opt/share/info/libtool \ >>>> > build/aix/configure.out >>>> + /opt/bin/make > build/aix/make.out >>>> extract-trace: error: One of these is required: >>>> extract-trace: gm4 gnum4 m4 >>>> extract-trace: error: Please install GNU M4, or 'export >>>> M4=/path/to/gnu/m4'. >>>> + /opt/bin/make install DESTDIR=/var/tmp/root/libtool-2.4.4.0 > >>>> build/aix/install.out >>>> libtool: warning: remember to run 'libtool --finish /opt/lib' >>>> + mkinstallp.ksh /var/tmp/root/libtool-2.4.4.0 > build/aix/mkinstallp.out >>>> + cat - >>>> + 0< /tmp/sh299200.1 1>> >>>> /data/prj/gnu/libtool/libtool-2.4.4/build/aix/aixtools.libtool.2.4.4.template >>>> + cat - >>>> + 0< /tmp/sh299200.1 1>> >>>> /data/prj/gnu/libtool/libtool-2.4.4/build/aix/aixtools.libtool.2.4.4.template >>>> + mkinstallp -d /var/tmp/root/libtool-2.4.4.0 -T >>>> /data/prj/gnu/libtool/libtool-2.4.4/build/aix/aixtools.libtool.2.4.4.template >>>> Using /var/tmp/root/libtool-2.4.4.0 as the base package directory. >>>> Cannot find /var/tmp/root/libtool-2.4.4.0/.info. Attempting to create. >>>> Using /var/tmp/root/libtool-2.4.4.0/.info to store package control files. >>>> Cleaning intermediate files from /var/tmp/root/libtool-2.4.4.0/.info. >>>> >>>> Using >>>> /data/prj/gnu/libtool/libtool-2.4.4/build/aix/aixtools.libtool.2.4.4.template >>>> as the template file. >>>> aixtools.libtool 2.4.4.0 I >>>> processing aixtools.libtool.rte >>>> processing aixtools.libtool.man >>>> processing aixtools.libtool.share >>>> creating ./.info/liblpp.a >>>> creating ./tmp/aixtools.libtool.2.4.4.0.bff >>>> ============================== >>>> aixtools.libtool:aixtools.libtool.man:2.4.4.0::I:T:::::N:built 1448 1201 >>>> 0942::::0:: >>>> aixtools.libtool:aixtools.libtool.rte:2.4.4.0::I:T:::::N:libtool 1448 1201 >>>> 0942::::0:: >>>> aixtools.libtool:aixtools.libtool.share:2.4.4.0::I:T:::::N:built 1448 1201 >>>> 0942::::0:: >>>> ============================== >>>> >>>> >>>> root@x064:[/data/prj/gnu/libtool/libtool-2.4.4]which m4 >>>> /usr/bin/m4 >>>> root@x064:[/data/prj/gnu/libtool/libtool-2.4.4]lslpp -w /usr/bin/m4 >>>> File Fileset Type >>>> >>>> ---------------------------------------------------------------------------- >>>> /usr/bin/m4 bos.adt.base Symlink >>>> root@x064:[/data/prj/gnu/libtool/libtool-2.4.4]ls -l /usr/bin/m4 >>>> lrwxrwxrwx 1 bin bin 15 Oct 31 15:55 /usr/bin/m4 -> /usr/ccs/bin/m4 >>>> root@x064:[/data/prj/gnu/libtool/libtool-2.4.4]lslpp -w /usr/ccs/bin/m4 >>>> File Fileset Type >>>> >>>> ---------------------------------------------------------------------------- >>>> /usr/ccs/bin/m4 bos.adt.base File >>>> root@x064:[/data/prj/gnu/libtool/libtool-2.4.4]lslpp -L bos.adt.base >>>> Fileset Level State Type Description >>>> (Uninstaller) >>>> >>>> ---------------------------------------------------------------------------- >>>> bos.adt.base 5.3.7.4 C F Base Application >>>> Development >>>> Toolkit >>>> So, my real question here: should the build have failed because it is not >>>> GNU m4? >>>> >>>>> On Mon, Dec 1, 2014 at 9:50 AM, Michael Felt <aixto...@gmail.com> wrote: >>>>> Hi Gary, >>>>> >>>>> Not to the list. Not so important. Since you mentioned to read the manual >>>>> I am "finding" where AIX shows up. >>>>> >>>>> 1) http://www-03.ibm.com/systems/power/software/aix/index.html - or >>>>> something else (not sure what >>>>> (http://www.rs6000.ibm.com/resource/aix_resource/Pubs/) on PDF page 94 >>>>> was pointing at) >>>>> 2) trying to understand this - question - is it ancient for all platforms? >>>>> powerpc-ibm-aix4.3.1.0 gcc 1.2f ok >>>>> (egcs-1.1.1) >>>>> powerpc-ibm-aix4.2.1.0 gcc 1.2f ok >>>>> (egcs-1.1.1) >>>>> powerpc-ibm-aix4.1.5.0 gcc 1.2f ok >>>>> (egcs-1.1.1) >>>>> powerpc-ibm-aix4.1.5.0 gcc 1.2f NS >>>>> (gcc-2.8.1) >>>>> powerpc-ibm-aix4.1.4.0 gcc 1.0 ok >>>>> powerpc-ibm-aix4.1.4.0 xlc 1.0i ok >>>>> rs6000-ibm-aix4.1.5.0 gcc 1.2f ok >>>>> (gcc-2.7.2) >>>>> rs6000-ibm-aix4.1.4.0 gcc 1.2f ok >>>>> (gcc-2.7.2) >>>>> rs6000-ibm-aix3.2.5 gcc 1.0i ok >>>>> rs6000-ibm-aix3.2.5 xlc 1.0i ok >>>>> 3) If #2 is not ancient - is there anyway I can help you update it for >>>>> AIX 5.3, 6.1 and 7.1? And maybe find someone else who can look at AIX 5.1 >>>>> and 5.2 - if that would be "nice"? >>>>> 4) IA-64 and AIX was never commercially released - only alpha - >>>>> pre-release test versions were ever made available (aka AIX 5.0). >>>>> 5) the PDF manual, although dated 29 Nov 2014 as file internally is For >>>>> version 2.4.2, 17 October 2011 - and I found no reference to the change >>>>> specified for AIX. >>>>> >>>>> sincerely, >>>>> Michael >>>>> >>>>>> On Sat, Nov 29, 2014 at 7:53 PM, Gary V. Vaughan <g...@gnu.org> wrote: >>>>>> Libtoolers! >>>>>> >>>>>> The Libtool Team is pleased to announce the release of libtool 2.4.4. >>>>>> >>>>>> GNU Libtool hides the complexity of using shared libraries behind a >>>>>> consistent, portable interface. GNU Libtool ships with GNU libltdl, which >>>>>> hides the complexity of loading dynamic runtime libraries (modules) >>>>>> behind a consistent, portable interface. >>>>>> >>>>>> This is a bugfix release to clean-up some of the small issues in 2.4.3 >>>>>> for which you kindly provided patches. There are still some known (and >>>>>> unknown!) regressions, especially on unusual platforms. Patches to fix >>>>>> those are not only welcome, but necessary to keep Libtool working in >>>>>> those places. >>>>>> >>>>>> Here are the compressed sources: >>>>>> http://ftpmirror.gnu.org/libtool/libtool-2.4.4.tar.gz (1.7MB) >>>>>> http://ftpmirror.gnu.org/libtool/libtool-2.4.4.tar.xz (936KB) >>>>>> >>>>>> Here are the GPG detached signatures[*]: >>>>>> http://ftpmirror.gnu.org/libtool/libtool-2.4.4.tar.gz.sig >>>>>> http://ftpmirror.gnu.org/libtool/libtool-2.4.4.tar.xz.sig >>>>>> >>>>>> Use a mirror for higher download bandwidth: >>>>>> http://www.gnu.org/order/ftp.html >>>>>> >>>>>> [*] Use a .sig file to verify that the corresponding file (without the >>>>>> .sig suffix) is intact. First, be sure to download both the .sig file >>>>>> and the corresponding tarball. Then, run a command like this: >>>>>> >>>>>> gpg --verify libtool-2.4.4.tar.gz.sig >>>>>> >>>>>> If that command fails because you don't have the required public key, >>>>>> then run this command to import it: >>>>>> >>>>>> gpg --keyserver keys.gnupg.net --recv-keys 151308092983D606 >>>>>> >>>>>> and rerun the 'gpg --verify' command. >>>>>> >>>>>> This release was bootstrapped with the following tools: >>>>>> Autoconf 2.69 >>>>>> Automake 1.14.1 >>>>>> Gnulib v0.1-270-g1b6c775 >>>>>> >>>>>> NEWS >>>>>> >>>>>> * Noteworthy changes in release 2.4.4 (2014-11-29) [stable] >>>>>> >>>>>> ** New features: >>>>>> >>>>>> - Libltdl maintains its own fork of argz, with macros and files in >>>>>> the LT_ and lt__ namespaces (resp.) where they cannot clash with >>>>>> client projects' use of gnulib argz. >>>>>> >>>>>> ** Bug fixes: >>>>>> >>>>>> - Installation of 'libtoolize' once again obeys '--program-prefix', >>>>>> '--program-suffix' and '--program-transform-name' configure options. >>>>>> >>>>>> - `libtoolize` doesn't remove any files that it can't reinstall, >>>>>> including old versions of the snippet directory, and gnulib's >>>>>> version of the argz module and supporting files. >>>>>> >>>>>> - LT_FUNC_DLYSM_USCORE now works correctly on systems that don't >>>>>> support self dlopen()ing. >>>>>> >>>>>> ** Important incompatible changes: >>>>>> >>>>>> - LT_LIB_DLLOAD no longer prepends -ldl or -ldld to LIBS, causing >>>>>> duplicate occurrences in libltdl link lines. If you need to >>>>>> add a library for dlopen() or shl_load() in your Makefile, then >>>>>> use $(LIBADD_DLOPEN) or $(LIBADD_SHL_LOAD) respectively. If you >>>>>> are using libltdl, this all happens automatically, and the only >>>>>> difference you'll see is no more duplicated library names in the >>>>>> verbose link line. >>>>>> >>>>>> ** Changes in supported systems or compilers: >>>>>> >>>>>> - Preliminary support for tcc on linux*. Although it already worked >>>>>> sometimes in previous releases, making sure to set LD correctly now >>>>>> avoids mis-matching GNU ld with tcc: >>>>>> >>>>>> ./configure CC=tcc LD=tcc >>>>>> >>>>>> - Added -os2dllname option to work around 8 character base name >>>>>> limit on OS/2. The option has no effect on other systems. >>>>>> >>>>>> - Support for DLL versioning, -export-symbols and -export-symbols-regex >>>>>> on OS/2. >>>>>> >>>>>> - Support filename-based shared library versioning on AIX. See manual >>>>>> for details. >>>>>> >>>>>> Enjoy! >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> GNU Announcement mailing list <info-...@gnu.org> >>>>>> https://lists.gnu.org/mailman/listinfo/info-gnu >
_______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool
