net-im/telepathy-haze Build fail
in [Ports]
|
From: Ruslan Mahmatkhanov on 28 Jul 2010 14:34 28.07.2010 22:26, David Southwell пишет: >> 28.07.2010 22:05, David Southwell пишет: >>>> 28.07.2010 21:57, Ruslan Mahmatkhanov пишет: >>>>> 28.07.2010 21:00, David Southwell пишет: >>>>>> Hi >>>>>> >>>>>> This is a python error. Is anyone sufficiently familiar with python to >>>>>> take a >>>>>> look at tools/glib-signals-marshall-gen.py. >>>>>> Is all the code in that script strict enough for python 3. >>>>>> >>>>>> David >>>>>> >>>>>> config.status: executing depfiles commands >>>>>> config.status: executing libtool commands >>>>>> ===> Building for telepathy-haze-0.3.6 >>>>>> gmake all-recursive >>>>>> gmake[1]: Entering directory >>>>>> `/usr/ports/net-im/telepathy-haze/work/telepathy- >>>>>> haze-0.3.6' >>>>>> Making all in tools >>>>>> gmake[2]: Entering directory >>>>>> `/usr/ports/net-im/telepathy-haze/work/telepathy- >>>>>> haze-0.3.6/tools' >>>>>> gmake[2]: Nothing to be done for `all'. >>>>>> gmake[2]: Leaving directory >>>>>> `/usr/ports/net-im/telepathy-haze/work/telepathy- >>>>>> haze-0.3.6/tools' >>>>>> Making all in extensions >>>>>> gmake[2]: Entering directory >>>>>> `/usr/ports/net-im/telepathy-haze/work/telepathy- >>>>>> haze-0.3.6/extensions' >>>>>> xsltproc --nonet --novalid --xinclude ../tools/identity.xsl \ >>>>>> all.xml> _gen/all.xml >>>>>> /usr/local/bin/python ../tools/glib-signals-marshal-gen.py >>>>>> _gen/all.xml> _gen/signals-marshal.list >>>>>> File "../tools/glib-signals-marshal-gen.py", line 49 >>>>>> print 'VOID:' + ','.join(rhs) >>>>>> ^ >>>>>> SyntaxError: invalid syntax >>>>> >>>>> As in gnome-terminal case you can patch it yourself like this: >>>>> print('VOID:' + ','.join(rhs)) >>>>> >>>>> instead >>>>> >>>>> print 'VOID:' + ','.join(rhs) >>>>> >>>>> but as i stated in my previous message, the wrong way is to use >>>>> python26 as your primary python version. >>>> >>>> the right way, i mean, or the wrong way is not to use python26 :) >>> >>> Here is an extract from my pkgdb from which you can see python26 is >>> installed on the system. If the port needs 26 surely should it not call >>> for it as a dependency rather than failiung because python31-3.1.2_1 is >>> present?? >>> >>> David >>> >>> dns1# pkg_info |grep python >>> python25-2.5.5_1 An interpreted object-oriented programming language >>> python26-2.6.5_1 An interpreted object-oriented programming language >>> python31-3.1.2_1 An interpreted object-oriented programming language >> >> And what your `python -V` tells? > python 3.1.2 > > Ok How do we deal with this? > Some apps need 3.1.2 -- > So maybe the ports using python should check for the environment and if > necessary force its own environment at build time with an appropriate setenv > call?? Is this not the correct procedure according to the porters handbook? > > David I believe by 'some apps' you mean applications that is not inside ports collection. So may be you create /usr/local/bin/python symlink to point on python2.6 as Chuck suggested and change #!/usr/bin/python string to #!/usr/bin/python3.1 in your applications. It's too much time will be passed until all the applications in ports tree migrate/be compatible with python3. -- Regards, Ruslan _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Chuck Swiger on 28 Jul 2010 14:37
On Jul 28, 2010, at 11:28 AM, David Southwell wrote: > I believe the porters handbook recomends that ports should set the appropriate > python environment at build time to prevent this problem occuring. Sure, modulo that setting USE_PYTHON isn't going to change the default Python which gets run when scripts do: #!/usr/bin/env python Again, at the present time, most things are going to want python-2.x; anything which is python-3.x should explicitly invoke python3. Regards, -- -Chuck _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |