Re: [gtk-osx-users] Issue with building GTK2.x for "modulesets" set (librsvg)

[John Ralls <jralls ceridwen us>]

> On Feb 29, 2016, at 9:53 PM, Miroslav Rajcic <mrajcic hotmail com> wrote:
>
> Just checked, here is my .jhbuildrc-custom:
>
> moduleset = 'https://raw.github.com/jralls/gtk-osx-build/master/modulesets/gtk-osx.modules' 
> setup_sdk(target="10.6", sdk_version="10.6", architectures=["i386"])
> os.environ["ARCHFLAGS"] = "-arch x86_64 -arch i386"
>
> The only thing I do manually is building an older version of libffi (v3.0.9) because the newer one fails to 
> build with older compile tools such as XCode 4.2 (https://github.com/atgreen/libffi/issues/128).
> Could this be related?
>
> I've retried the build from clean state, and I still get this issue:
>
> Makefile.am:217: error: HAVE_INTROSPECTION does not appear in AM_CONDITIONAL
> Makefile.am: installing './depcomp'
> tests/Makefile.am:27: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> parallel-tests: installing './test-driver'
> tools/Makefile.am:10: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> autoreconf: automake failed with exit status: 1
> *** Error during phase configure of librsvg: ########## Error running ./autogen.sh --prefix 
> /Users/helix/gtk/inst --disable-Bsymbolic   *** [35/38]
>
> If you want to inspect the log, the full log is given here:
> http://notecase.sourceforge.net/temp/putty.zip

Miroslav,

I don't think that libffi has anything to do with anything, but FWIW I build 3.0.13 by shelling out after 
3.2.1 fails then
  cd ..
  rm -rf libffi-3.2.1
  tar -xf ../gtk-downloads/libffi-3.0.13.tar.gz
  mv libffi-3.0.13 libffi-3.2.1
  ^d
and then re-running configure. That makes jhbuild think that it built libffi-3.2.1 successfully, so it 
doesn't ignore any of the dependencies.

You seem to be running jhbuild out of a master shell script that runs bootstrap then builds python and a 
target called "modules". Dunno what that last one includes, but meta-gtk-osx-bootrap doesn't seem to be in 
it. It needs to be, it provides a bunch of dependencies that aren't necessarily explicitly depended upon by 
downstream modules. Also jhbuild works best if you tell it upfront everything it needs to do all at once; it 
can use the dependency tree to make an optimal build order. If you tell it what to build piecemeal that 
shifts more of the responsibility to you to get everything needed in the right order.

Maybe you could post the script that you're using?

The exception to that rule is building a Python3 app, because gobject-introspection doesn't work with Python3 
so all of the introspected C libraries need to be built first, then Python3, then gtk-osx-integration-python 
if you're using it, then switch the "python" link to point at python3 (because a couple of 
pygobject-dependent custom configure scripts are stupid) and build the rest. A serious PITA, but probably not 
what your dealing with.

Regards,
John Ralls