Re: python27 update-py-psyco
On 3/8/11, ajtiM lum...@gmail.com wrote: On Monday March 7 2011 08:37:46 b. f. wrote: On 3/7/11, ajtiM lum...@gmail.com wrote: On Sunday March 6 2011 12:01:47 b. f. wrote: Thank you. I am reading /usr/ports/UPDATING special like now but there are problems. And I have a problem again with /usr/ports/devel/py-psyco I get: c/mergepoints.c:242: error 'JUMP_IF_FALSE' undeclared here *** Error code 1 ... Thank you very much for reply but I see that is not possible to build it (I red about psyco on mailing list). For now everything works but I have more ports to rebuild but psyco is the big problem. Well, I'm not sure what list you are referring to here, but you should still be able to build it, if you set PYTHON_VERSION to python2.5 or python2.6 in your build environment, on the command-line, or in any included Makefile (like, for example, /etc/make.conf or $PORTSDIR/devel/py-psyco/Makefile.local). Of course, if you are using psyco with some other software, then you may have to do the same for that software. You can do that conditionally if you are doing it in some common Makefile like /etc/make.conf, and still want to use other software with another version of python. For example: .if${.CURDIR:M*/ports/devel/py-psyco} PYTHON_VERSION=python2.6 .endif b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: python27 update-py-psyco
On Sunday March 6 2011 12:01:47 b. f. wrote: I am using portmaster all the time more or less without problems. I like to switch to portupgrade but I don't know if is good to mix them. I think I will wait to FreeBSD 9 and than install evrything from scratch. You would have encountered the problem that you mentioned regardless of whether you used portupgrade or portmaster, and the results would have been the same. It was a flaw in the ports tree itself, not in the updating tool. I think that portmaster is probably a better choice for most people, since it implements most if not all of the features that portupgrade does, the maintainer is more active, and it doesn't need ruby and bdb to work, or require extra databases. Mixing portupgrade and portmaster shouldn't cause any problems, as long as you take care to keep your portupgrade port and package databases up-to-date, but it probably isn't necessary to use both. Whatever you decide, I urge you to take a few minutes to read the manpage of your updating tool. It can save you a lot of time and frustration later. Also, if you want to avoid problems, after major changes to the ports tree, it is safer to wait for a few days before updating your own ports. Usually there are a few problems that are uncovered and fixed after major changes are made, and it takes a few days or a week for this to happen. b. Thank you. I am reading /usr/ports/UPDATING special like now but there are problems. And I have a problem again with /usr/ports/devel/py-psyco I get: c/mergepoints.c:242: error 'JUMP_IF_FALSE' undeclared here *** Error code 1 I trid make clean and make again but it is the same. Thanks. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: python27 update-py-psyco
On 3/7/11, ajtiM lum...@gmail.com wrote: On Sunday March 6 2011 12:01:47 b. f. wrote: Thank you. I am reading /usr/ports/UPDATING special like now but there are problems. And I have a problem again with /usr/ports/devel/py-psyco I get: c/mergepoints.c:242: error 'JUMP_IF_FALSE' undeclared here *** Error code 1 There is not enough context here to learn much, but this is the kind of error that could occur if this port is built with python 2.7.x. It may be that your ports tree is still not up-to-date, because this is one of the few ports that doesn't work with python 2.7.x [The upstream maintainer was working on a new version (see the port website), but hasn't finished it yet], so Martin modified the port: http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/devel/py-psyco/Makefile.diff?r1=1.17;r2=1.18 Do you have those changes? Is py-psyco using python 2.5.x or 2.6.x during the build? If not, update your ports tree (and make sure that it really _is_ up-to-date, by looking at the file afterward, because some mirrors have been having problems lately), then (for safety) rebuild whatever version of python (2.5.x or 2.6.x) you are using with py-psyco, and then try again. If it still doesn't work, post your full build log to the freebsd-python mailing list. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: python27 update-py-psyco
On Monday March 7 2011 08:37:46 b. f. wrote: On 3/7/11, ajtiM lum...@gmail.com wrote: On Sunday March 6 2011 12:01:47 b. f. wrote: Thank you. I am reading /usr/ports/UPDATING special like now but there are problems. And I have a problem again with /usr/ports/devel/py-psyco I get: c/mergepoints.c:242: error 'JUMP_IF_FALSE' undeclared here *** Error code 1 There is not enough context here to learn much, but this is the kind of error that could occur if this port is built with python 2.7.x. It may be that your ports tree is still not up-to-date, because this is one of the few ports that doesn't work with python 2.7.x [The upstream maintainer was working on a new version (see the port website), but hasn't finished it yet], so Martin modified the port: http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/devel/py-psyco/Makefile.diff?r1 =1.17;r2=1.18 Do you have those changes? Is py-psyco using python 2.5.x or 2.6.x during the build? If not, update your ports tree (and make sure that it really _is_ up-to-date, by looking at the file afterward, because some mirrors have been having problems lately), then (for safety) rebuild whatever version of python (2.5.x or 2.6.x) you are using with py-psyco, and then try again. If it still doesn't work, post your full build log to the freebsd-python mailing list. b. Thank you very much for reply but I see that is not possible to build it (I red about psyco on mailing list). For now everything works but I have more ports to rebuild but psyco is the big problem. Thanks again... Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: python27 update
On Sat, 5 Mar 2011 19:53:22 -0800 Nerius Landys nlan...@gmail.com articulated: Sadly, this is one of those times when portupgrade seems to handle things better, but you'll probably have to wait another day to see if things worked out better this time. For me, using portupgrade on 3 different systems (7.4 and 8.1) to upgrade Python 2.6 to 2.7 worked like a charm. Just my two cents. +1 -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: python27 update
Jerry writes: Sadly, this is one of those times when portupgrade seems to handle things better, but you'll probably have to wait another day to see if things worked out better this time. For me, using portupgrade on 3 different systems (7.4 and 8.1) to upgrade Python 2.6 to 2.7 worked like a charm. Just my two cents. +1 Here also. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: python27 update
On Sunday March 6 2011 08:09:01 Robert Huff wrote: Jerry writes: Sadly, this is one of those times when portupgrade seems to handle things better, but you'll probably have to wait another day to see if things worked out better this time. For me, using portupgrade on 3 different systems (7.4 and 8.1) to upgrade Python 2.6 to 2.7 worked like a charm. Just my two cents. +1 Here also. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I am using portmaster all the time more or less without problems. I like to switch to portupgrade but I don't know if is good to mix them. I think I will wait to FreeBSD 9 and than install evrything from scratch. Thank you to everyone for the help... Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: python27 update
I am using portmaster all the time more or less without problems. I like to switch to portupgrade but I don't know if is good to mix them. I think I will wait to FreeBSD 9 and than install evrything from scratch. You would have encountered the problem that you mentioned regardless of whether you used portupgrade or portmaster, and the results would have been the same. It was a flaw in the ports tree itself, not in the updating tool. I think that portmaster is probably a better choice for most people, since it implements most if not all of the features that portupgrade does, the maintainer is more active, and it doesn't need ruby and bdb to work, or require extra databases. Mixing portupgrade and portmaster shouldn't cause any problems, as long as you take care to keep your portupgrade port and package databases up-to-date, but it probably isn't necessary to use both. Whatever you decide, I urge you to take a few minutes to read the manpage of your updating tool. It can save you a lot of time and frustration later. Also, if you want to avoid problems, after major changes to the ports tree, it is safer to wait for a few days before updating your own ports. Usually there are a few problems that are uncovered and fixed after major changes are made, and it takes a few days or a week for this to happen. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: python27 update
On 5 March 2011 21:52, ajtiM lum...@gmail.com wrote: My system: 8.2-RELEASE FreeBSD 8.2-RELEASE #0 I tried to update python26 to python27. I did as I red in /usr/ports/UPDATING: portmaster -o lang/python27 lang/python26 and than cd /usr/ports/lang/python make upgrade-site-packages -DUSE_PORTMASTER and after one day and a half of pressing yes for deleting old files I got: - error: Comand cc - shared -pthread -02 -pipe -WI, -rpath -/usr/local/lib/gcc45 -fno -strict -aliasing build/temp. freebsd-8.2-RELEASE- i386-2.7/build/src.freebsd-8.2-RELEASE-i386-2.7/numpy/core/src/-sortmudele.o - Lbuild/temp.freebsd-8.2-RELEASE-i386-2.7-lm -o build/lib-freebsd-8.2-RELEASE- i386-2.7/numpy/core/-sortss failed with exit status 1 ***Error code 1 Stop in /usr/ports/math/py-numpy =make failed for math/py-numpy = Aborting update = Update fpr py26-numpy-1.5.1,1 failled Aborting update Update for opencv-2.1.0 failed aborting update Terminated ***Error code 143 Stop in /usr/ports/lang/python Is it possible to save this problem, please? Do I need run again cd /usr/ports/lang/python make upgrade-site-packages -DUSE_PORTMASTER and wait one day more or will portmaster continue where it stopped? I thought portmaster usually spit out a sort of to resume where you left off, issue 'portmaster blah blah blah' message when something barfed like that. Set up your /usr/local/etc/portmaster.rc with one of: # Never search for stale distfiles to delete (-D) # DONT_SCRUB_DISTFILES=Dopt # # Always delete stale distfiles without prompting (-d) # ALWAYS_SCRUB_DISTFILES=dopt (see /usr/local/etc/portmaster.rc.sample) to avoid the Delete this file? prompts every three minutes. Sadly, this is one of those times when portupgrade seems to handle things better, but you'll probably have to wait another day to see if things worked out better this time. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: python27 update
Sadly, this is one of those times when portupgrade seems to handle things better, but you'll probably have to wait another day to see if things worked out better this time. For me, using portupgrade on 3 different systems (7.4 and 8.1) to upgrade Python 2.6 to 2.7 worked like a charm. Just my two cents. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: python27 update
... I tried to update python26 to python27. I did as I red in /usr/ports/UPDATING: portmaster -o lang/python27 lang/python26 and than cd /usr/ports/lang/python make upgrade-site-packages -DUSE_PORTMASTER and after one day and a half of pressing yes for deleting old files I got: Has it been a day and a half already? ;) Seriously, though, read the portmaster manpage and learn how you can take some shortcuts, like running 'portmaster -y --clean-distfiles', or using other flags to lower the amount of interaction required. - error: Comand cc - shared -pthread -02 -pipe -WI, -rpath -/usr/local/lib/gcc45 -fno -strict -aliasing build/temp. freebsd-8.2-RELEASE- i386-2.7/build/src.freebsd-8.2-RELEASE-i386-2.7/numpy/core/src/-sortmudele.o - Lbuild/temp.freebsd-8.2-RELEASE-i386-2.7-lm -o build/lib-freebsd-8.2-RELEASE- i386-2.7/numpy/core/-sortss failed with exit status 1 ***Error code 1 Stop in /usr/ports/math/py-numpy =make failed for math/py-numpy = Aborting update = Update fpr py26-numpy-1.5.1,1 failled Aborting update Update for opencv-2.1.0 failed aborting update Terminated ***Error code 143 Stop in /usr/ports/lang/python You need to update your ports tree to make sure that you pick up: http://lists.freebsd.org/pipermail/cvs-ports/2011-March/213081.html which should fix the above problem. Is it possible to save this problem, please? Do I need run again cd /usr/ports/lang/python make upgrade-site-packages -DUSE_PORTMASTER and wait one day more or will portmaster continue where it stopped? Try: ... make upgrade-site-packages -DUSE_PORTMASTER PORTUPGRADE_ARGS=-R Even if that doesn't work, you won't have to repeat all of your previous work, because those ports that were successfully updated in the last run will no longer have files in the old python26 library directories, and so won't be rebuilt by re-running upgrade site-packages, unless you were to run portmaster with additional flags. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org