On Mon, Oct 26, 2009 at 12:17 PM, John Ralls <jra...@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 <jra...@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.
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list
