Summary: | editors/vim BROKEN not buildable on RELENG_9 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Chris Hutchinson <portmaster> | ||||||
Component: | Individual Port(s) | Assignee: | Po-Chuan Hsieh <sunpoet> | ||||||
Status: | Closed Unable to Reproduce | ||||||||
Severity: | Affects Many People | CC: | portmaster | ||||||
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(sunpoet) |
||||||
Version: | Latest | ||||||||
Hardware: | Any | ||||||||
OS: | Any | ||||||||
Attachments: |
|
Auto-assigned to maintainer sunpoet@FreeBSD.org Created attachment 152521 [details]
Build log for editors/cream editors/vim-7.45
Please update the ports tree, update perl to 5.18 or above and then build editors/vim (not editors/cream) again. (In reply to Sunpoet Po-Chuan Hsieh from comment #3) > Please update the ports tree, update perl to 5.18 or above and then build > editors/vim (not editors/cream) again. So this is a Perl [version] issue? If so, the version of Perl on the box I attempted to build this port on, was supported. Last I looked on a recent -CURRENT (11); the Perl [EOL] is a warning, not FATAL. As such; I would argue this is still a problem with this port (or vim), and the port should check against the currently installed (default_)version(s) of Perl, and issue a WARN, or FATAL, as required. Also; wouldn't it be prudent to only provide [port] versions that are compliant with the requirements still in force on each RELENG_ branch? Thank you for all your time, and consideration, Sunpoet. --Chris I just tested editors/vim(-lite) in a 9.3-RELEASE-p9 jails using poudriere. It builds with error. I would like to close this PR. |
Created attachment 152520 [details] build log for editors/cream editors/vim-7.44 In an attempt to build/install editors/cream, editors/vim was sucked in as a dependency. The attempted build failed (logs attached). Failing to see an immediate solution, I tarred up the editors/vim folder, and sucked down the most recent version via svn(1). Then attempted the build with that version. Which also failed at seemingly the same place. Please find 2 complete build sessions attached, for complete details. Thank you for all your time, and consideration. --Chris