Date: Thu, 07 Aug 2014 07:45:20 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 192449] lang/python27 fails to build on FreeBSD 11 Message-ID: <bug-192449-21822-DAfMF4ba4T@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192449-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-192449-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192449 --- Comment #7 from cipher_nl@hotmail.com --- Thanks for the pointer. I scripted the retrieval of the information like this: MAKECONF_OSVERSION=`/bin/cat /usr/include/sys/param.h | grep "^#define __FreeBSD_version" | cut -d\ -f 3 | cut -f 1` MAKECONF_UNAME_R=`/bin/cat /usr/src/release/doc/share/xml/release.ent | grep "release.branch" | cut -d\" -f 2` MAKECONF_UNAME_V=`/bin/cat /usr/src/release/doc/share/xml/release.ent | grep "release.branch" | cut -d\" -f 2` echo >> /etc/make.conf echo -n "${MAKECONF_UNAME_R}" >> /etc/make.conf echo -n "${MAKECONF_UNAME_V}" >> /etc/make.conf echo -n "${MAKECONF_OSVERSION}" >> /etc/make.conf The result is the following being added to /etc/make.conf prior to building: UNAME_r=11-CURRENT UNAME_v=11-CURRENT OSVERSION=1100028 However, i still get the same build failure. It still fails with: pkg-static: lstat(/usr/ports/lang/python27/work/stage/usr/local/lib/python2.7/plat-freebsd11/IN.py): No such file or directory pkg-static: lstat(/usr/ports/lang/python27/work/stage/usr/local/lib/python2.7/plat-freebsd11/IN.pyo): No such file or directory pkg-static: lstat(/usr/ports/lang/python27/work/stage/usr/local/lib/python2.7/plat-freebsd11/IN.pyc): No such file or directory pkg-static: lstat(/usr/ports/lang/python27/work/stage/usr/local/lib/python2.7/plat-freebsd11/regen): No such file or directory pkg-static: lstat(/usr/ports/lang/python27/work/stage/usr/local/lib/python2.7/plat-freebsd11/): No such file or directory *** Error code 74 Interestingly, initially i set OSVERSION to the SVN revision, which started with a '2'. This changed the failure in python27, saying "freebsd2" instead of "freebsd11". So it does appear that the setting is used. But perhaps there is an additional problem why python27 is not compiling. Is there any more diagnosis that can be done? Thanks for the help! -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192449-21822-DAfMF4ba4T>