Bug 196237 - sysutils/php5-fileinfo fails to build (clang bug?)
Summary: sysutils/php5-fileinfo fails to build (clang bug?)
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-23 20:14 UTC by alan
Modified: 2015-09-15 21:56 UTC (History)
3 users (show)

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

Attachments
Error output from attempts to make port (5.37 KB, text/plain)
2014-12-23 20:14 UTC, alan 		no flags Details
File requested by error message (522 bytes, text/plain)
2014-12-23 20:16 UTC, alan 		no flags Details
File requested by error message (compressed) (741.35 KB, application/x-gzip)
2014-12-23 20:17 UTC, alan 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description alan 2014-12-23 20:14:30 UTC 
Created attachment 150918 [details]
Error output from attempts to make port

sysutils/php5-fileinfo, fresh portsnap update (yesterday anyhow), freebsd 10.1
Comment 1 Bugzilla Automation freebsd_committer freebsd_triage 2014-12-23 20:14:30 UTC 
Auto-assigned to maintainer ale@FreeBSD.org
Comment 2 alan 2014-12-23 20:15:43 UTC 
requested file apprentice-3cf1fb.c is 17M and too large to upload
Comment 3 alan 2014-12-23 20:16:25 UTC 
Created attachment 150919 [details]
File requested by error message
Comment 4 alan 2014-12-23 20:17:40 UTC 
Created attachment 150920 [details]
File requested by error message (compressed)
Comment 5 alan 2014-12-23 20:18:29 UTC 
(In reply to alan from comment #2)
> requested file apprentice-3cf1fb.c is 17M and too large to upload

Was able to upload by compressing
Comment 6 Alex Dupre freebsd_committer freebsd_triage 2014-12-24 08:15:43 UTC 
It seems a clang bug, I cannot fix it.
Comment 7 John Marino freebsd_committer freebsd_triage 2015-02-09 21:36:50 UTC 
what is going on here?

The maintainer will not own the PR just because he can't fix this?  If he can't, who can?  Who will?

By definition, the maintainer should own the PRs on his port.  I don't know why the maintainer will not keep this.  Especially since he doesn't bother to say why he returned it to the pool.


Well, it's been triaged, so it's no longer "new".  I'm setting this to "open".
Comment 8 Jason Unovitch freebsd_committer freebsd_triage 2015-06-02 00:59:42 UTC 
Is this valid or can it be closed?  Portsmon is reporting php5-fileinfo (and php55-fileinfo/php56-fileinfo for that matter) as being green on all platforms.

http://portsmon.freebsd.org/portoverview.py?category=sysutils&portname=php5-fileinfo&wildcard=

http://portsmon.freebsd.org/portoverview.py?category=sysutils&portname=php55-fileinfo&wildcard=

http://portsmon.freebsd.org/portoverview.py?category=sysutils&portname=php56-fileinfo&wildcard=

Additionally for submitter, what was going on behind the scenes here?  What was this from:
 x86_64-unknown-freebsd10.1

I see this when I compile the php5-fileinfo.  Could this have been self inflicted from some kind of customization?
 amd64-portbld-freebsd10.1

Jason
Comment 9 alan 2015-06-08 09:21:48 UTC 
Nothing special behind the scenes, just a fresh install of freebsd and then some ports.  I just did a portsnap update to see if the problem still occurred, but it wants to update php, except it's complaining that "php5-5.4.41 has known vulnerabilities" (duh, it's php ;-) ) and I don't have time to fight with it right now...