On Tue, 3 Jul 2001, Skip Montanaro wrote:
>
> In a freshly checked out gnome-python directory, I executed ./autogen.sh and
> got
>
> 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 .
> aclocal -I macros
> aclocal: couldn't open `configure.in': No such file or directory
> automake --add-missing
> automake: couldn't open `configure.in': No such file or directory
> autoconf
> autoconf: configure.in: No such file or directory
> Processing ./pygtk
> aclocal
> automake --add-missing
> autoconf
> ./configure
> ./autogen.sh: ./configure: No such file or directory
>
> Now type 'make' to compile gnome-python.
You should work from the pygtk directory, rather than the top level
gnome-python directory. I haven't started on the gnome 2.0 wrappers yet
(partly waiting til the ORBit-python has a chance to look at things).
There is another autogen script in the pygtk directory that should work
fine (autoconf seems to have some problems if it finds a configure.in in
the directory above it, which is why I removed the toplevel one).
>
> Ignoring that, I cd'd to pygtk and executed ./configure:
>
[snip]
> sed: can't read ./codegen/pygtk-codegen-2.0.in: No such file or directory
> creating config.h
>
> I copied the version from the 7/3 snapshot and will try building with it.
Forgot to cvs add that file. Will do it now.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
