Re: Fortran libraries on the Blue Gene with mpi
Ralf Wildenhues wrote: * Christian Rössel wrote on Tue, Apr 21, 2009 at 10:28:37AM CEST: Ralf Wildenhues wrote: If there are any problems or error messages, stop right here and report back with them. Otherwise, continue: There was one error I assume is negligible: cd ./doc \ makeinfo --no-headers -o notes.txt notes.texi /bin/sh: makeinfo: command not found Yes, the error itself should be harmless, but it has the problem of causing some other files not to be built. Please re-bootstrap with MAKEINFO=true ./bootstrap then there should be a libtoolize.in file afterwards, and you should be able to go on with the previous list, unless there are further errors. Hi Ralf, re-boostrapping works now but the missing makeinfo causes new problems: /u/fzj301zm/BlueGene/fortran_libraries_on_the_blue_gene_with_mpi/libtool/libltdl/config/missing: line 54: makeinfo: command not found WARNING: `makeinfo' is missing on your system. You should only need it if you modified a `.texi' or `.texinfo' file, or any other file indirectly affecting the aspect of the manual. The spurious call might also be the consequence of using a buggy `make' (AIX, DU, IRIX). You might want to install the `Texinfo' package or the `GNU make' package. Grab either from any GNU archive site. make[2]: *** [../doc/libtool.info] Error 1 I will install makeinfo to avoid further problems. I'll apply the patch below to let the impact of missing 'makeinfo' be less of a problem, if you let me know which email address to add to THANKS. Use christian.roes...@gmx.de Cheers, Christian
Re: Fortran libraries on the Blue Gene with mpi
Ralf Wildenhues wrote: First, please ensure that you have Autoconf 2.63 and Automake 1.10.2 installed somewhere (below the same --prefix) and found early in $PATH. Hi Ralf, why do I need to install them below the *same* prefix. Is this a general requirement? What will happen if I use distinct prefixes but put both bindirs into my PATH? Regards, Christian
Re: Fortran libraries on the Blue Gene with mpi
On Wed, 22 Apr 2009, Christian Rössel wrote: Ralf Wildenhues wrote: First, please ensure that you have Autoconf 2.63 and Automake 1.10.2 installed somewhere (below the same --prefix) and found early in $PATH. why do I need to install them below the *same* prefix. Is this a general requirement? What will happen if I use distinct prefixes but put both bindirs into my PATH? Installation under the same prefix is necessary because the installed m4 files from the various packages share a directory and that is where aclocal looks for them. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Re: Fortran libraries on the Blue Gene with mpi
Christian Rössel wrote: Ralf Wildenhues wrote: * Christian Rössel wrote on Tue, Apr 21, 2009 at 10:28:37AM CEST: Ralf Wildenhues wrote: If there are any problems or error messages, stop right here and report back with them. Otherwise, continue: There was one error I assume is negligible: cd ./doc \ makeinfo --no-headers -o notes.txt notes.texi /bin/sh: makeinfo: command not found Yes, the error itself should be harmless, but it has the problem of causing some other files not to be built. Please re-bootstrap with MAKEINFO=true ./bootstrap then there should be a libtoolize.in file afterwards, and you should be able to go on with the previous list, unless there are further errors. Hi Ralf, re-boostrapping works now but the missing makeinfo causes new problems: /u/fzj301zm/BlueGene/fortran_libraries_on_the_blue_gene_with_mpi/libtool/libltdl/config/missing: line 54: makeinfo: command not found WARNING: `makeinfo' is missing on your system. You should only need it if you modified a `.texi' or `.texinfo' file, or any other file indirectly affecting the aspect of the manual. The spurious call might also be the consequence of using a buggy `make' (AIX, DU, IRIX). You might want to install the `Texinfo' package or the `GNU make' package. Grab either from any GNU archive site. make[2]: *** [../doc/libtool.info] Error 1 I will install makeinfo to avoid further problems. Hi Ralf, I installed makeinfo (texinfo-4.13) and re-bootstrapped ... # GCC, non-BG cd build-gcc ../configure CC=gcc CXX=g++ F77=g77 FC=gfortran GCJ=no make ... and ran into the next error: /u/fzj301zm/BlueGene/fortran_libraries_on_the_blue_gene_with_mpi/libtool/libltdl/config/missing: line 54: help2man: command not found WARNING: `help2man' is missing on your system. You should only need it if you modified a dependency of a manual page. You may need the `Help2man' package in order for those modifications to take effect. You can get `Help2man' from any GNU archive site. gmake[2]: *** [../doc/libtoolize.1] Error 1 After installing help2man I was able to run the tests. Cheers, Christian
Re: [patch #6691] FreeMiNT support to libtool 1.5.26 (tested)
Hello Alan, thanks for the feedback. I've added the libtool-patches mailing list in Cc:, hope you don't mind (the savannah tracker entries get mailed there anyway). * Alan Hourihane wrote on Wed, Apr 22, 2009 at 06:09:33PM CEST: These came up as the failures. The tests 16 73 seems to be exposing a linker bug that I'm looking at now. I'm sure the others are due to the fact that FreeMiNT doesn't have shared libraries or dlopen support. So I guess I need to tweak some other configuration files someplace. Can you send the tests/testsuite.log file also? Thanks! If you know where to poke that, let me know and I can re-test. The log file would help immensely in being able to tell that. The Run tests with low max_cmd_len test (73) is typically a followup failure of other test failures (it internally reruns some tests). 16: duplicate_conv.at:25 duplicate convenience archive names libtool 41: old-m4-iface.at:107 AC_WITH_LTDL libtoolize automake autoconf 44: lt_dlexit.at:30lt_dlexit unloading libs libltdl 45: lt_dladvise.at:28 lt_dlopenadvise library loading libltdl 51: standalone.at:79 linking libltdl without autotools libtoolize 55: subproject.at:109 linking libltdl without autotools libtoolize 69: configure-iface.at:159 --with-ltdl-include/lib libltdl libtoolize automake autoconf 70: configure-iface.at:225 --with-included-ltdl libltdl libtoolize automake autoconf 73: cmdline_wrap.at:28 Run tests with low max_cmd_len recursive Cheers, Ralf
Re: Fortran libraries on the Blue Gene with mpi
Hello Christian, * Christian Rössel wrote on Wed, Apr 22, 2009 at 11:21:27AM CEST: Ralf Wildenhues wrote: First, please ensure that you have Autoconf 2.63 and Automake 1.10.2 installed somewhere (below the same --prefix) and found early in $PATH. why do I need to install them below the *same* prefix. Is this a general requirement? What will happen if I use distinct prefixes but put both bindirs into my PATH? You don't *have* to install all autotools below the same prefix. However, we generally recommend this, because that way we avoid the questions of what *exactly* can go wrong and how, and what to do in those cases. ;-) I'll try a more precise description: it is usually possible to install Autoconf, Automake, Libtool, and other packages that provide macro files, below different prefixes. If you do so, however, then you need to ensure that aclocal (which is part of the Automake package) finds those third-party macro files which can reside at LIBTOOL_PREFIX/share/aclocal OTHER_PACKAGES_PREFIXES/share/aclocal The way I usually solve this is by using a dirlist file: I add the lines LIBTOOL_PREFIX/share/aclocal OTHER_PACKAGE1_PREFIX/share/aclocal OTHER_PACKAGE2_PREFIX/share/aclocal to the AUTOMAKE_PREFIX/share/aclocal/dirlist file, all prefixes suitably expanded of course. Subtle problems can appear if there is more than one set of Libtool macro files among the directories that aclocal searches, and they came from different Libtool releases; so please avoid that situation. Likewise for other third-party packages that provide macro files. Hope that helps. Cheers, Ralf
Re: Fortran libraries on the Blue Gene with mpi
* Christian Rössel wrote on Wed, Apr 22, 2009 at 06:28:51PM CEST: re-boostrapping works now but the missing makeinfo causes new problems: /u/fzj301zm/BlueGene/fortran_libraries_on_the_blue_gene_with_mpi/libtool/libltdl/config/missing: line 54: makeinfo: command not found WARNING: `makeinfo' is missing on your system. You should only need it if you modified a `.texi' or `.texinfo' file, or any other file indirectly affecting the aspect of the manual. The spurious call might also be the consequence of using a buggy `make' (AIX, DU, IRIX). You might want to install the `Texinfo' package or the `GNU make' package. Grab either from any GNU archive site. make[2]: *** [../doc/libtool.info] Error 1 I will install makeinfo to avoid further problems. I installed makeinfo (texinfo-4.13) and re-bootstrapped ... Yeah, sorry about that, I should have known that you would also need to use make MAKEINFO=true ... and ran into the next error: /u/fzj301zm/BlueGene/fortran_libraries_on_the_blue_gene_with_mpi/libtool/libltdl/config/missing: line 54: help2man: command not found WARNING: `help2man' is missing on your system. You should only need it if you modified a dependency of a manual page. You may need the `Help2man' package in order for those modifications to take effect. You can get `Help2man' from any GNU archive site. gmake[2]: *** [../doc/libtoolize.1] Error 1 After installing help2man I was able to run the tests. This, OTOH, is a bug that will be fixed in the next Automake release. The need for help2man will then only arise for make dist, even with version control checkouts which contain no pre-generated man pages. However, for others encountering this bug: you can also work around it by repeatedly running make for a few times. I've pushed the patch for bootstrap now. Cheers, and thanks for persevering, Ralf
