RE: [Gtk2hs-users] Can't configure gtk2hs

[Duncan C. <dun...@wo...>]

On Wed, 2005-03-16 at 10:49 +0000, Simon Marlow wrote:
> On 16 March 2005 09:39, Simon Marlow wrote:
> 
> > On 16 March 2005 09:22, Martin Sjögren wrote:
> >> I don't know about Fedora, but Debian makes a difference between
> >> devel and non-devel packages. E.g. gtksourceview-1.0.pc is in
> >> libgtksourceview-dev, not in libgtksourceview1.0-0.
> > 
> > Duh, that's it.  Thanks.
> 
> I still can't build 0.7.1 with GHC 6.4, looks like a problem related to the different -I handling in GHC 6.4.

We have a patch for 0.9.7 for GHC 6.4, see this email:
http://sourceforge.net/mailarchive/forum.php?thread_id=6731116&forum_id=8415

(though apparently I messes up the patch preperation, as Gour says it
does not apply cleanly. No matter for the patch is just two one line
changes.)

> So I checked out the CVS version of gtk2hs, and I can't figure out how to build that:
> 
> ~/tmp/gtk2hs > autoreconf
> autom4te: unknown language: Autoconf-without-aclocal-m4
> aclocal: autom4te failed with exit status: 1
> autoreconf: aclocal failed with exit status: 1

Here's my guess (and perhaps you can help us with this since you're an
autotools user):

When you first run autoreconf it picks a version of automake to run.
Sometimes this is too old a version of automake. I beleieve we require
automake 1.8 or something. So after running with a particular version of
automake then after that autoreconf will always use that version.

So the hacky solution is to just manually run automake-1.8 (possibly
deleting cache files if it complains about them being created by older
automate versions). Then after that run
$ autoreconf -i

and it should then do the right thing.

It's not clear to me how we force autoreconf/automake to use the right
version because if we stick AUTOMAKE_OPTIONS = 1.8 then I seem to recall
autoreconf just stopped because the vesion of automake it invoked
stopped as soon as it realised it was the wrong version! *&8$*
autotools.

Though actually, trying that myself just now seemed to work, maybe it
was the upgrade to autoreconf 2.59 or something. I'll add it so that at
least it'll work for newer autoreconf and on older ones it might give a
more informative error message than what you got.

Duncan