`./configure` and `./builds/unix/configure.ac` are identical in my
post-`autogen.sh` git copy and my 2.5.3 archive copy of the source code
(except for a handful of minor changes to letter casing in `configure.ac`).
Are there any other critical files that I can `diff`?
Is it not the case that the error message saying that it does not
understand the macro name `AC_INIT`?
/Volumes/DATA/filestore/development/c/libs/freetype2/git/freetype2/builds/unix/configure:
> line 1: syntax error near unexpected token `('
> /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])'
> make: *** [setup] Error 2
Could this be because a file is missing? Where does autoconf resolve these
macro lookups from?
config.mk:25:
> /Volumes/DATA/filestore/development/c/libs/freetype2/git/freetype2/builds/unix/
> unix-def.mk: No such file or directory
> config.mk:26:
> /Volumes/DATA/filestore/development/c/libs/freetype2/git/freetype2/builds/unix/
> unix-cc.mk: No such file or directory
> make: *** No rule to make target
> `/Volumes/DATA/filestore/development/c/libs/freetype2/git/freetype2/builds/unix/
> unix-cc.mk'. Stop.
`unix-def.mk` does not exist, and neither does `unix-cc.mk` in my git
source code, but then they do not in the archive source code either. Are
they supposed to be generated temporarily by `autoconf` and then deleted?
There are similarly named files in both copies of the `unix` directory.
On 19 June 2014 14:43, Jeffrey Sheen <[email protected]> wrote:
> Thanks Werner, I'm going to try one more thing before burdening you.
>
> I only migrated from the 2.5.3 archive copy of the source code, as there
> was a bug fix in the git repository. The `configure` command was working
> correctly for OSX in that archive.
>
> Who built that `configure` script for the archive, and did they use OSX?
> I'm going to `diff` the two files and see if there are any substantive
> differences.
>
>
> On 19 June 2014 14:20, Werner LEMBERG <[email protected]> wrote:
>
>>
>> >> /usr/bin/make
>> >
>> > Does this also have to be under the same prefix tree?
>>
>> No. Note that `have to' is probably not correct, but it has
>> simplified my life in the last few years...
>>
>> Well, I'm out of ideas. Please do the following within FreeType's git
>> repository
>>
>> git clean -fdx
>> ./autogen.sh &> autogen.sh.log
>> ./configure &> configure.log
>>
>> and send me privately the files `autogen.sh.log', `configure.log', and
>> `builds/unix/config.log' (compressed) so that I can have a closer
>> look.
>>
>>
>> Werner
>>
>
>
_______________________________________________
Freetype mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype
