James Henstridge wrote:
> On Wed, 9 May 2001, Lennon Day-Reynolds wrote:
>
> > I'm not sure where it *supposed* to come from, but I was able to get a
> > copy of python.m4 (the Automake macro for Python configuration options)
> > from the CVS version of Ammonite. I've attached it in case anyone else
> > is having problems -- drop it in your aclocal directory ('aclocal
> > --print-ac-dir' for the uncertain).
> >
> > I'm still having problems with the build on RH7, but am working through
> > them; on SuSE 7, though, the newest CVS version absolutely refuses to
> > compile -- something to do with their screwy placement of all the GNOME
> > core libraries and apps, I think.
>
Thanks for attaching the macro definition, I found it shows up in the
aclocal.m4 of pygtk package so I just copy and paste it to dia's
acinclude.m4.
>
> I have no idea why you are seeing this problem. The macro is in
> acinclude.m4, so should get coppied into aclocal.m4 and get used.
>
> The AM_PATH_PYTHON macro in CVS automake sucks, which is why I made the
> modified AM_PATH_PYTHON_JH macro (the changes are being fed upstream),
> which says it provides AM_PATH_PYTHON, so the other macros should use it.
> I don't know what is causing the problems for you.
>
>From acinclude.m4, I saw AM_PATH_PYTHON_JH is defined, and it uses
AC_PROVIDE([AM_PATH_PYTHON]). I am not very sure what AC_PROVIDE is doing
yet (just from the manual of Autoconf), but I think it is asking for the
AM_PATH_PYTHON macro.
By the way, my autoconf and automake version is up-to-date according to the
README/INSTALL file.
I was able to get the aclocal.m4 generated after attaching the AM_PATH_PYTHON
macro definition at the end of acinclude.m4.
>
> Does the tarball release work okay? (other than the missing
> python-startup.py problem :(
I haven't tried the tarball release, but the latest CVS works ok for me
except the missing file problem (therefore no python support in dia for me
yet).
Patrick
