Bug 215551 - lang/python36: packaging failure
Summary: lang/python36: packaging failure
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Antoine Brodin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-25 17:33 UTC by Konstantin Belousov
Modified: 2017-04-01 07:11 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (python)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin Belousov freebsd_committer freebsd_triage 2016-12-25 17:33:01 UTC
I got the following errors during build of python 3.6

pkg-static: Unable to access file /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/lib/python3.6/__pycache__/_sysconfigdata_m_freebsd11_.cpython-36.opt-1.pyc: No such file or directory
pkg-static: Unable to access file /wrkdirs/usr/ports/lang/python36/work/stage/usr/local/lib/python3.6/__pycache__/_sysconfigdata_m_freebsd11_.cpython-36.opt-2.pyc: No such file or directory

etc.

Full log is available at https://www.kib.kiev.ua/kib/python36-3.6.0.log
Comment 1 Wen Heping freebsd_committer freebsd_triage 2016-12-26 02:27:16 UTC
I can not reproduce it on FreeBSD-11 amd64 release.

Maybe the problem is your os is _OSRELEASE=11.0-RC3 ?

wen
Comment 2 Konstantin Belousov freebsd_committer freebsd_triage 2016-12-26 09:03:59 UTC
(In reply to Wen Heping from comment #1)
I do not think so.  I get the same or almost same problem for i386 10.3 build as well:
https://www.kib.kiev.ua/kib/10-i386-python36-3.6.0.log

Did you noted that I use non-standard options ?
Comment 3 Wen Heping freebsd_committer freebsd_triage 2016-12-26 14:35:35 UTC
r429525 committed by antoine@ fix the problem.

wen
Comment 4 Wen Heping freebsd_committer freebsd_triage 2016-12-26 14:39:14 UTC
r429525 committed by antoine@ fix the problem.

wen
Comment 5 Konstantin Belousov freebsd_committer freebsd_triage 2016-12-26 19:52:48 UTC
Fix worked for me, thanks.