Re: [Orbit-python-list] Does not compile from CVS / Debian package?

[Brad C. <cha...@ar...>]

On 2 Aug 2000, Roland Mas wrote:
>   I got the latest version from the Sourceforge CVS server, and I'm
> wondering how to make it compile.
>   OK, so the INSTALL file says to run ./configure.  This script does
> not exist.  But the INSTALL file also says that this script can be
> generated with autoconf. 

Right, from CVS you need to run the autoconf tools (aclocal, autoconf and
automake) to generate configure from configure.in. But, as you discovered,
the autogen.sh script will do this for you automatically.

>   Hm.  OK, I'll try something else.  There's a ./autogen.sh script.
> Doesn't work either.  Output from a freshly checked-out tree:
> 
> /---- CUT -----
> | roland@minimir:~/perso/src/orbit-python$ ./autogen.sh 
> | I am going to run ./configure with no arguments - if you wish 
> | to pass any to it, please specify them on the ./autogen.sh command line.
> | processing .
> | You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'.
> | aclocal: configure.in: 7: macro `AM_INIT_PYEXEC_MOD' not found in library
> | aclocal: configure.in: 8: macro `AM_PATH_PYTHON' not found in library

Automake 1.4, unfortunately, doesn't have support for python, so you'll
need to apply James Henstridge's patches to automake to make it work, you
can get them from
http://cds.duke.edu/pub/sunsite/X11/gtkbuffet/lang/pygtk/pyautomake.tar.gz
(or another mirror if one is better for you). If you follow the
instructions in there to patch automake and get the macros in the right
place, this should clear up these two errors, and hopefully this will let
./autogen.sh go through cleanly for you. 
	If you still have problems after this, please ask again.

HTH,
Brad