Re: Building Gtk-OSX (was: Intricate changes to Quartz/OSX backend)

[John Ralls <jralls ceridwen us>]

On Oct 26, 2009, at 9:35 AM, Paul Davis wrote:

> On Mon, Oct 26, 2009 at 12:17 PM, John Ralls <jralls ceridwen us>  
> wrote:
> > On Oct 26, 2009, at 9:07 AM, Paul Davis wrote:
> >
> > > On Mon, Oct 26, 2009 at 11:07 AM, John Ralls <jralls ceridwen us>  
> > > wrote:
> > >
> > > > When I've encountered that in the past it's been because Python  
> > > > was too
> > > > old:
> > > > Jhbuild's tarball.py uses a function that's only available in  
> > > > Python 2.5.
> > > > While jhbuild bootstrap will install a new Python for you on  
> > > > Tiger (which
> > > > comes with Python 2.3), the new version isn't used to run jhbuild  
> > > > itself
> > > > unless you tell it to.
> > >
> > > turns out that this was not the issue. basically, even my jhbuild  
> > > was
> > > too old to get this right. a new build is underway, but its now died
> > > claiming that we need m4 1.4 or later, and i have 1.4.13 ... sigh.
> > > digging in.
> >
> > Having installed the new jhbuild, did you run jhbuild bootstrap?  
> > Remember
> > that jhbuild sets the path to find its own stuff first.
>
> the downloaded autoconf-2.63 contains this line:
>
> my $m4 = $ENV{"M4"} || '@M4@';
>
> both LHS halves of which evaluate to $gtk_prefix/inst/bin/m4 even
> though jbhuild has not built m4 at this stage.

Um, how long ago did you last run jhbuild bootstrap? The m4 module was  
added to bootstrap.modules last December, with version 1.4.11. The  
autoconf module depends upon it, so it should be installed before  
autoconf. .jhbuildrc, if you're using the one from Gtk-OSX, sets M4= 
$PREFIX/bin/m4. That happens after jhbuildrc-custom is imported, so  
you'll have to edit .jhbuildrc directly if you want to use another  
one. Just don't try to use the one Apple provides (but you probably  
already know that).

Regards,
John Ralls