Date: Sun, 6 Apr 2014 10:18:53 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: "koobs@FreeBSD.org" <koobs@FreeBSD.org> Cc: "ports@freebsd.org" <ports@freebsd.org>, Shane Ambler <FreeBSD@ShaneWare.Biz> Subject: Re: Python install catch 22 Message-ID: <A53E2351-13D1-49D0-873A-2E4A3BACFF46@digiware.nl> In-Reply-To: <5340BA4E.7010306@FreeBSD.org> References: <533EA19E.80905@digiware.nl> <533F7CF4.6070003@ShaneWare.Biz> <EAA9A178-4EDC-4E06-8DA4-4B131D3F5A8F@digiware.nl> <5340BA4E.7010306@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Op 6 apr. 2014 om 04:22 heeft Kubilay Kocak <koobs.freebsd@gmail.com> het vo= lgende geschreven: > On 5/04/2014 9:12 PM, Willem Jan Withagen wrote: >>=20 >>=20 >> Op 5 apr. 2014 om 05:48 heeft Shane Ambler <FreeBSD@ShaneWare.Biz> het vo= lgende geschreven: >>=20 >>> On 04/04/2014 22:42, Willem Jan Withagen wrote: >>>> Hi, >>>>=20 >>>> I've tried to upgrade my python 2.7 which did not work. >>>> Then I deinstalled all python stuff and tried to install python3 (aka 3= .3) >>>=20 >>> You can install both versions of python (2.7 & 3.3) at the same time, >>> but currently you can only install a module to one of the versions at a >>> time. >>=20 >> Sorry, >>=20 >> I did not explain the situation clear enough. >>=20 >> I was at 2.7, and wanted to install a 2.7 upgrade because of a bug. >> If memory serves me, from 2.7.3 to 2.7.6 >>=20 >> But that started mounting about missing db stuff, and having to install a= py/db of choice. >> That is where I ran into the catch22, installing a db required py-tools, w= hich in turn starts to try to upgrade python from 2.7.3 to 2.7.6. >=20 > Hi Willem, >=20 > a) Can you clarify/confirm whether you tried installing/upgrading Python > via ports or packages. Ports. To be honnest, i only considered packages, after you mentioned them. >=20 > b) Tell us exactly (method & commands) how you attempted to upgrade > Python 2.7 to Python 3.3 Sorry that I've still not been clear. The upgrade was needed because 'pkg audit' reported a bug. I used 'portupgrade python27' to get to the most python27.=20 The 'portinstall python33' was only to see if that would not have the same p= roblem. I first removed all dependant on python27. >=20 > b) If via ports, it would be helpful to know how and why the dbm module > fails to build for python33 >=20 > Either attach a complete build log here, or join us on IRC > #freebsd-python on freenode so we can help you isolate. I'll see if I have some time today to get this going, an will get you the lo= g. --WjW >=20 > Koobs >=20 >=20 >> Then I cleaned/removed al python stuff, and tried again. >> First with 2.7 and when that did not work, I tried 3.3 with the same resu= lt. >> I tried with portinstall/portupgrade as well as make && make install, but= both fail for the same reason. >>=20 >> So atm I have no python at al. >>=20 >>> So far there are still many modules that don't work with 3.x so you may >>> want to use 2.7 if you want python with more than the default modules. >>>=20 >>> The default python is still 2.7, if you want to use 3.3 then you might >>> want to add >>> DEFAULT_VERSIONS=3DPYTHON=3D3.3 PYTHON3=3D3.3 >>> to your /etc/make.conf >>>=20 >>>> The system everytime refuses to install because of missing a database: >>>>=20 >>>> pkg-static: >>>> lstat(/home2/usr/ports/lang/python33/work/stage/usr/local/lib/python3.3= /lib-dynload/_dbm.so): >>>> No such file or directory >>>> *** [fake-pkg] Error code 74 >>>>=20 >>>> [ replace python33 by python27 te get the similar error for 2.7 ] >>>=20 >>> This would indicate that the dbm module wasn't built. It should be built= >>> and is a module that gives access to others that may be installed from >>> the list below. The db modules below don't need to be installed first >>> for _dbm.so to be built. >>>=20 >>> This is an error compiling not related to the other modules. If your >>> using a gui then scrollback in the terminal to see the error - increase >>> scrollback limit if needed, from cli maybe use script to keep a log of >>> the build to look through. >>=20 >> Using command line in putty. >> I will try again, and scan de build output for more errors. So there shou= ld be an error building the part in the stage tree? >>=20 >>=20 >>>=20 >>> gettext libiconv and gmake are the only things that need to be installed= >>> before python to build. >>=20 >> So where does it get the DBMS stuff from? >>=20 >>> Maybe there is an issue with you not building >>> from /usr/ports ? >>=20 >> That would be a first. This config is like this for about 6 years. >> And /user/ports links to this tree. >>=20 >>>=20 >>>> And then hints: >>>> =3D=3D=3D=3D >>>> Note that some of the standard modules are provided as separate >>>> ports since they require extra dependencies: >>>>=20 >>>> gdbm databases/py-gdbm >>>> sqlite3 databases/py-sqlite3 >>>> tkinter x11-toolkits/py-tkinter >>>>=20 >>>> Install them as needed. >>>> =3D=3D=3D=3D >>>>=20 >>>> Which is nasty catch22, because one needs a recent/working python to >>>> actually be able to do this. >>>>=20 >>>> How do other cope with this? >>>>=20 >>>=20 >>> Could using pkg to install a prebuilt binary package be an option? >>=20 >> That would be the alternative, but I only do that, if nothing else works.= >> I've grown to always build my stuff. >>=20 >>>=20 >>> What FreeBSD version are you using? >>=20 >> I386 9.2-STABLE >>=20 >> --WjW >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >>=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A53E2351-13D1-49D0-873A-2E4A3BACFF46>