Hi Gary, * Gary V. Vaughan wrote on Tue, Mar 29, 2005 at 11:56:02AM CEST: > Ralf Wildenhues wrote: > >>All fine, except that you need to 'cd $(srcdir)' first in the make rule, > > > > I don't understand why this should be necessary; it breaks use of $<. > > I put it in the patch below, though. > > Yes, but I'm not sure we're allowed to use $< in automake rules anyway > (incase the package builder has a degenerate make installed).
Ah, yes, thank you. [ snip golden rule explanations ] > > > I had to change a couple more details -- setting SUFFIXES does not work > > with the hacked-up Makefile, so I went for a simple rule. > > Thats probably better for automake anyhow. Yep. > > One more question: Do you think we should install notes.txt? > > No, the info manual contains all the information, and is the right place > to document a GNU package. Unless you wanted to add a libtoolize option > to copy it into a package's source tree... as LIBTOOL maybe? That might > help to raise the profile of the notes section, and generate more bug > reports against it so we can keep it up to date. I have no strong feelings > about that either way. Hmm. I'm reluctant to add files to people's trees, even more so with generic names. I have applied the following patch to HEAD. Given no problems come up with it, I can backport to branch-2-0 eventually. The pgCC notes are pending a couple of PGI patches, which will go in soonish. :) Regards, Ralf 2005-04-04 Ralf Wildenhues <[EMAIL PROTECTED]> * notes.texi: Platform-specific configuration notes. * doc/libtool.texi: Include as section. * bootstrap, doc/Makefile.am: build also as notes.txt and distribute. --- /dev/null 2005-04-04 11:53:15.417024464 +0200 +++ doc/notes.texi 2005-03-30 13:15:59.000000000 +0200 @@ -0,0 +1,48 @@ [EMAIL PROTECTED] + [EMAIL PROTECTED] +On AIX there are two different styles of shared linking, one in which symbols +are bound at link-time and one in which symbols are bound at runtime only, +similar to [EMAIL PROTECTED] In case of doubt use @code{LDFLAGS=-Wl,-brtl} for the latter style. + [EMAIL PROTECTED] +For C++ code with templates, it may be necessary to specify the way the compiler +will generate the instantiations. For Portland pgCC version5, use [EMAIL PROTECTED]'pgCC --one_instantiation_per_object'} and avoid parallel @command{make}. + [EMAIL PROTECTED] +FreeBSD @command{make} does not conform to @sc{posix} in its handling +of file modification times, which causes it to loop while building libtool. +Consider using a different @command{such} as GNU make instead. + [EMAIL PROTECTED] +The default shell on UNICOS 9, a ksh 88e variant, is too buggy to +correctly execute the libtool script. Users are advised to install a +modern shell such as GNU bash. + [EMAIL PROTECTED] +Some HP-UX @command{sed} programs are horribly broken, and cannot handle +libtool's requirements, so users may report unusual problems. There +is no workaround except to install a working @command{sed} (such as GNU sed) +on these systems. + [EMAIL PROTECTED] +The vendor-distributed NCR MP-RAS @command{cc} programs emits copyright +on standard error that confuse tests on size of @file{conftest.err}. The +workaround is to specify @env{CC} when run configure with [EMAIL PROTECTED]'cc -Hnocopyr'}. + [EMAIL PROTECTED] +Any earlier DG/UX system with ELF executables, such as R3.10 or +R4.10, is also likely to work, but hasn't been explicitly tested. + [EMAIL PROTECTED] +On Reliant Unix libtool has only been tested with the Siemens C-compiler +and an old version of @command{gcc} provided by Marco Walther. + [EMAIL PROTECTED] [EMAIL PROTECTED], @file{ltdl.m4} and the @file{configure.ac} files are marked +to use autoconf-mode, which is distributed with GNU Emacs 21, Autoconf itself, +and all recent releases of XEmacs. + [EMAIL PROTECTED] itemize Index: bootstrap =================================================================== RCS file: /cvsroot/libtool/libtool/bootstrap,v retrieving revision 1.59 diff -u -r1.59 bootstrap --- bootstrap 15 Mar 2005 12:58:40 -0000 1.59 +++ bootstrap 4 Apr 2005 17:28:04 -0000 @@ -32,6 +32,7 @@ : ${FGREP=fgrep} : ${SED=sed} : ${LN_S='ln -s'} +: ${MAKEINFO=makeinfo} test -f ./configure.ac || { echo "bootstrap: can't find ./configure.ac, please rerun from top_srcdir" @@ -63,7 +64,7 @@ # Whip up some dirty Makefiles: makefiles= -for dirty in ./Makefile ./tests/Makefile +for dirty in ./Makefile ./tests/Makefile ./doc/Makefile do test -f $dirty || { makefiles="$makefiles $dirty" @@ -90,6 +91,9 @@ $MAKE ./testsuite AUTOTEST="$AUTOM4TE --language=autotest" \ srcdir=. top_srcdir=.. PACKAGE="$2" VERSION="$3" cd .. + cd doc + $MAKE notes.txt srcdir=. top_srcdir=.. MAKEINFO="${MAKEINFO}" + cd .. } test -f clcommit.m4sh && $MAKE -f Makefile.maint commit \ Index: doc/Makefile.am =================================================================== RCS file: /cvsroot/libtool/libtool/doc/Makefile.am,v retrieving revision 1.4 diff -u -r1.4 Makefile.am --- doc/Makefile.am 25 Nov 2003 15:48:22 -0000 1.4 +++ doc/Makefile.am 4 Apr 2005 17:28:04 -0000 @@ -1,4 +1,10 @@ ## Process this file with automake to produce Makefile.in info_TEXINFOS = libtool.texi -libtool_TEXINFOS = PLATFORMS fdl.texi +libtool_TEXINFOS = PLATFORMS fdl.texi notes.texi +EXTRA_DIST = notes.txt + +all-local: notes.txt + +notes.txt: notes.texi + cd $(srcdir) && $(MAKEINFO) --plaintext $(MAKEINFOFLAGS) -o $@ notes.texi Index: doc/libtool.texi =================================================================== RCS file: /cvsroot/libtool/libtool/doc/libtool.texi,v retrieving revision 1.190 diff -u -r1.190 libtool.texi --- doc/libtool.texi 28 Mar 2005 09:15:09 -0000 1.190 +++ doc/libtool.texi 4 Apr 2005 17:28:05 -0000 @@ -140,6 +140,7 @@ Configuring libtool * LT_INIT:: Configuring @code{libtool} in @file{configure.ac}. +* Configure notes:: Platform-specific notes for configuration. Including libtool in your package @@ -1825,6 +1826,7 @@ @menu * LT_INIT:: Configuring @code{libtool} in @file{configure.ac}. +* Configure notes:: Platform-specific notes for configuration. @end menu @node LT_INIT @@ -2122,6 +2124,16 @@ @end example [EMAIL PROTECTED] Configure notes [EMAIL PROTECTED] Platform-specific configuration notes + +While Libtool tries to hide as many platform-specific features as possible, +some have to be taken into account when configuring either the Libtool package +or a libtoolized package. + [EMAIL PROTECTED] notes.texi + + @node Distributing @section Including libtool in your package