Hi Werner, An interesting, and confusing, distinction for OSX. However, I could not find versions of the autotool binaries with a preceding 'g'.
To ensure that I am using GNU commands, I checked their versions with the `--version` option: automake (GNU automake) 1.14.1 > Copyright (C) 2013 Free Software Foundation, Inc. > License GPLv2+: GNU GPL version 2 or later < > http://gnu.org/licenses/gpl-2.0.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > > Written by Tom Tromey <[email protected]> > and Alexandre Duret-Lutz <[email protected]>. autoconf (GNU Autoconf) 2.69 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+/Autoconf: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html > > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. > Written by David J. MacKenzie and Akim Demaille. >From that output, these appear to be genuine GNU commands, and above the minimum versions required in `README.git`. However, the output for `libtool` certainly indicates an Apple binary: > Apple Inc. version cctools-855 > Could this be why `configure` is erroring out? On 18 June 2014 06:23, Werner LEMBERG <[email protected]> wrote: > > > generating `configure.ac' > >> running `aclocal -I . --force' > >> running `glibtoolize --force --copy --install' > >> glibtoolize: putting auxiliary files in `.'. > > [...] > > This looks correct. > > >> > /Volumes/DATA/filestore/development/c/libs/freetype2/git/freetype2/builds/unix/ > >> unix.mk > > This too. > > > > /Volumes/DATA/filestore/development/c/libs/freetype2/git/freetype2/builds/unix/configure: > >> line 1: `m4trace:configure.ac:14: -1- AC_INIT([FreeType], [2.5.3], [ > >> [email protected]], [freetype])' > > This essentially means that some macros haven't been properly expanded. > > > I believe I am following the installation procedure correctly. Any > > help you could offer would be greatly appreciated. > > The very thing is that under OS X the GNU autotool binaries often have > the prefix `g', and that there are similar, native Apple tools > (without the leading `g') that do something completely different, > probably based on programs with a BSD background. > > Please ensure that you are *really* using GNU autoconf and automake! > > > Werner >
_______________________________________________ Freetype mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype
