Thanks Werner. I take it that freetype2 is rarely built in OSX? I am using a stock Mavericks install, with the latest version of Xcode, and GNU autotools built with macports. If my environment is broken, then I'd suggest every OSX environment starts off broken too.
I'll try installing autotools manually, without using macports, and clean my git repository as you suggest. When we get this working, I'll write a blog post so that OSX/iOS developers can get started without seeking help from the mailing list. Cheers, Jeff. > On 18 Jun 2014, at 19:09, Werner LEMBERG <[email protected]> wrote: > > >> As the `autoconf` and `automake` commands appear valid, I am not >> sure how to proceed. > > It's not clear to me why your `builds/unix/configure' script has `(' > in the first line! It should *always* start with a comment, namely > with > > #! /bin/sh > > So there are severe problems in your setup, and it's hard to help with > a better diagnosis. > > If I have problems with the GNU autotools, I usually install autoconf, > automake, and libtool (and probably m4 also) with the same `--prefix' > configure option (e.g., `--prefix=/usr/local'), regardless whether > they exist on the host OS or not. I thus suggest that you do that, > too. Then simply prepend the related binary directory to your PATH > (/usr/local/bin) and restart with `git clean -fdx'. > > > Werner _______________________________________________ Freetype mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype
