On Sat, 26 Dec 1998, David M. Cook wrote:
> On Sat, Dec 26, 1998 at 08:16:12PM -0500, Bradford Hovinen wrote:
>
> > how to fix it? I'm running Python 1.5.1 and Gtk+ 1.1.9 on Redhat 5.1.
>
> I had some problems with Gtk 1.1.9. They were solved by upgrading to the
> 12/20 snapshot. I had a hard time trying to generate a configure script for
> the snapshot, so I stole the configure script from the 1.1.9 tarball.
Thanks.
I just downloaded and installed the latest snapshot from CVS, but it did
not fix the problem. I'm still getting the same error I was getting
before.
Incidentally, automake also aborts complaining about bad macro names:
Makefile.am:9: bad macro name `_gtkmodule__SO__SOURCES'
Makefile.am:10: bad macro name `_gtkmodule__SO__LDADD'
Makefile.am:11: bad macro name `_gtkmodule__SO__LINK'
Makefile.am:14: bad macro name `_gdkimlibmodule__SO__SOURCES'
Makefile.am:15: bad macro name `_gdkimlibmodule__SO__LDADD'
Makefile.am:16: bad macro name `_gdkimlibmodule__SO__LINK'
Also, aclocal complains of undefined macros:
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
> Dave Cook
> To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
-Bradford Hovinen
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
