Re: gnome-python-1.0.2 compile probs

[James Henstridge <james daa com au>]

The Makefile.am's in gnome-python use some extensions to automake that I
wrote (but haven't got round to sending in for inclusion in later versions
of automake).  If you want to hack on gnome-python, you will need to patch
your copy of automake.  The instructions and patches are available in the
am-changes directory of the gnome-python module on CVS.

James.

--
Email: james@daa.com.au
WWW:   http://www.daa.com.au/~james/


On Wed, 28 Apr 1999, James Green wrote:

> Hi gnomers,
> 
> I patched to gnome-python-1.0.2 and made clean, etc. ./configured. Then:
> 
> [jg@cyberstorm gnome-python-1.0.2]$ make
> Making all in macros
> make[1]: Entering directory `/usr/src/gnome/gnome-python-1.0.2/macros'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/usr/src/gnome/gnome-python-1.0.2/macros'
> Making all in pygtk
> make[1]: Entering directory `/usr/src/gnome/gnome-python-1.0.2/pygtk'
> cd . && aclocal
> aclocal: configure.in: 7: macro `AM_PATH_PYTHON' not found in library
> aclocal: configure.in: 8: macro `AM_INIT_PYEXEC_MOD' not found in library
> aclocal: configure.in: 10: macro `AM_CHECK_PYMOD' not found in library
> make[1]: *** [aclocal.m4] Error 1
> make[1]: Leaving directory `/usr/src/gnome/gnome-python-1.0.2/pygtk'
> make: *** [all-recursive] Error 1
> 
> Hm. I deleted the entire directory and untarred 1.0.0, and patched up
> again to 1.0.2 to get a fresh package. Still errors. I note in configure:
> 
> checking for python module thread... no
> 
> yet 1.0.1 compiled fine. Any ideas?
> 
> Running the new gnome-libs-1.0.9 too. AMD-k6-2, RedHAat5.2. Lots of
> tarballs replacing RPMs but it works :)
> 
> Everything latest AFAIK.
> 
> James Green
> 
> 
> 
> 
> -- 
>         FAQ: Frequently-Asked Questions at http://www.gnome.org/gnomefaq
>          To unsubscribe: mail gnome-list-request@gnome.org with 
>                        "unsubscribe" as the Subject.
>