Re: [ft] Question: linker errors when building freetype for iOS in Xcode

[Jeffrey Sheen]

Werner,

I think we are reading the error message incorrectly. The `configure` script does indeed start with a shell invocation (`#!/bin/sh').

The error is being thrown when the first parenthesis is encountered in `configure.ac`.

Given it is `m4trace` that is producing the error message, I checked the installed version of `m4`:

GNU M4 1.4.6

Copyright (C) 2006 Free Software Foundation, Inc.

This is free software; see the source for copying conditions.  There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Written by Rene' Seindal.

Which tool is interpreting this `configure.ac`? Should this file also start with a shell invocation, as it does not?

Should everything in parentheses in `configure.ac` have been replaced during the autotools procedure? Or is the format of the line in the error correct, and the tool that is interpreting it unfit for purpose?

On 18 June 2014 21:56, Jeff Sheen <address@hidden> wrote:

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 <address@hidden> 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