On 04/06/2012 05:49 PM, Stuart Stegall wrote: > Another update - apparently it's "complicated" ... > >> From the Python Modules BLFS page: PyGObject-3.0.3 provides Python 3 > bindings to the GObject class from GLib. - This is not true, these are > Python2 AND Python3 bindings and the py2cairo/pycairo requirements > must match as py2cairo/pycairo ARE version specific modules. > > libffi still stands as optional. > > py2cairo's build instructions are also incorrect as there's apparently > something missing with autoconfigure files, but waf IS included, so it > can be installed like: ./waf --prefix=/usr configure; ./waf build; > ./waf install > > Hopefully this is the correct list for these corrections. > > Go n-éirí leat, > Stuart > > > > On Fri, Apr 6, 2012 at 10:35 AM, Stuart Stegall<[email protected]> wrote: >> I have found that the current version of PyGObject requires PyCairo >> and can optionally use libffi. Py2cairo is actually listed on the old >> version of PyGObject. >> >> Go n-éirí leat, >> Stuart
There, everything should be fixed in revision 9865. But do note, there was autoreconf command which regenerated autotools files so configure could be used. But, I changed commands to ./waf since I like that one more (and including that, I could overcome some more evil libtool archives). -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
