Footnotes

(1)

See section 13. Rolling Distribution Tarballs

(2)

A number chosen arbitrarily by the Automake developers.

(3)

This book is built using automake and autoconf. We couldn't find a use for libtool.

(6)

An #include cycle is the situation where file `a.h' #includes file `b.h', and `b.h' #includes file `a.h' -- either directly or through some longer chain of #includes.

(7)

For an explanation of name mangling See section Writing Portable C++ with GNU Autotools.

(9)

Available at ftp://sourceware.cygnus.com/pub/binutils/.

(10)

Distributed from https://www.iro.umontreal.ca/~pinard/libit.

(11)

GCC must be compilable by K&R compilers so that it can be built and installed in an ANSI compiler free environment.

(12)

AIX and Windows being the main culprits.

(14)

Generally this involves indexing the symbols exported from the archive for faster linking, and to allow the archived objects to reference symbols from other objects earlier in the same archive.

Application Binary Interface: the layout of the bytes that comprise binary objects and executables: 32 or 64 bit words; procedure calling conventions; memory alignment rules; system call interface; order and type of the binary sections (data, code etc) and so on.

(16)

As is often the case, AIX is peculiar in this respect -- ranlib adds path information to a static archive, and must be run again after the archive is installed. libtool knows about this, and will automatically bless the installed library again on AIX.

(17)

When making a binary package from a virtual root directory for example.

(18)

`AM_PROG_LIBTOOL' if you have an older automake or libtool installation.

(19)

Position Independent Code -- suitable for shared libraries which might be loaded to different addresses when linked by the runtime loader.

(20)

The functionality of `ltconfig' is slated for migration into `libtool.m4' for a future release of libtool, whereupon this file will no longer be necessary.

(21)

ftp://ftp.gnu.org/gnu/config/

(22)

Actually the suffix will be whatever is appropriate for the target host: such as `.obj' on Windows for example.

(23)

For example, when I come to using the `make dist' rule.

(24)

The GNU standard is distributed from https://www.gnu.org/prep/standards.html.

(25)

This is for Autoconf version 2.13. Autoconf version 2.50 recommends AC_CONFIG_COMMANDS.

(26)

This is a sort of callback function which will be called by the make rules generated by Automake.

(27)

By default, GNU tar can create non-portable archives in certain (rare) situations. To be safe, Automake arranges to use the `-o' compatibility flag when GNU tar is used.

(28)

Probably numbered 1.5.

(29)

There has been some debate in the Autoconf community about extending Autoconf to allow new directories to be set on the configure command line. Currently the consensus seems to be that there are too many arguments to configure already.

(30)

The most common way being to simply set prefix.

(31)

This example assumes the use of GNU tar when extracting; this is standard on Linux but does not come with Solaris.

(32)

These names come from Gulliver's Travels.

(33)

https://sourceware.cygnus.com/cygwin/

(34)

https://www.scriptics.com/

(35)

Windows does permit a program to use a forward slash to separate directories when calling routines such as `fopen'. However, Windows users do not expect to type forward slashes when they enter file names, and they do not expect to see forward slashes when a file name is printed.

(36)

Visit the Libtool home page at https://www.gnu.org/software/libtool for breaking news.

(37)

https://www.mozilla.org/hacking/portable-cpp.html

(38)

Not essential but will be slower without this option, see 10.2.1 Position Independent Code.

(39)

HP-UX being the most notable exception.

(40)

As I always like to say, `from BeOS to Windows!'. And yes, I do think that it is a better catchphrase than `from AIX to Xenix'!

(41)

Use `AM_PROG_LIBTOOL' if you have automake version 1.4 or older or a version of libtool earlier than 1.4.

(42)

Architectures which use ELF and ECOFF binary format for example.

(43)

Those which use a.out binary format, for example.

(44)

https://www.gnu.org/software/dld

(45)

If you have an early 1.3c snapshot of Libtool, you will also need to copy the `ltdl.m4' file into your distribution.

(46)

This is very different to the way errors are managed when writing a custom loader for libltdl. Compare this section with Loader Errors.

(47)

See section 18.1 Introducing libltdl

(48)

Dmalloc is distributed from https://www.dmalloc.com.

(49)

GNU M4 permits an unlimited number of arguments, whereas other versions of M4 limit the number of addressable arguments to nine.

(50)

Which is precisely what the ``' and `'' characters in all of the examples in this section are.

(51)

The ``' is used in grave redirection and `'' for the shell's own quote character!

(52)

Notable exceptions are GNU Bash, and both Ksh and the Bourne shell on Solaris.

(53)

This is a literal newline.

(54)

A term coined by Noah Friedman in the early days of Autoconf to denote the process of converting a package that configures itself without Autoconf to one which does.

(55)

See https://sourceware.cygnus.com/java/

(56)

Mingw32 home page, https://www.geocities.com/Tokyo/Towers/6162/gcc.html; and DJGPP home page, https://www.delorie.com/djgpp/.

(57)

since Cygwin-b20.1, I believe.

(58)

1.1.1 at the time of writing.

(59)

ftp://ftp.gnu.org/gnu/make/make-3.79.tar.gz

(60)

You can get a precompiled package from https://cygutils.netpedia.net/, also an excellent resource for other packages ported to Cygwin.

(61)

https://sourceware.cygnus.com/cygwin/

(62)

The CygUtils website is https://cygutils.netpedia.net/V1.1/.

(63)

Typically you would also have a floppy drive named `A:', and a CD-ROM named `D:'.

(64)

See section 10.5 Executing Uninstalled Binaries.

(65)

In general, a stub function will satisfy the linker's requirements to resolve an undefined symbol at link time, but has no functionality of its own. In this context, the stubs do have some boilerplate code to pass execution flow into the correct full function in the DLL.