Summary: | print/fontforge poudriere build error | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Ivan Klymenko <fidaj> | ||||||||||||||
Component: | Individual Port(s) | Assignee: | Matthias Andree <mandree> | ||||||||||||||
Status: | Closed FIXED | ||||||||||||||||
Severity: | Affects Some People | CC: | cyberbotx, dim, hiroo.ono+freebsd, mandree | ||||||||||||||
Priority: | --- | Keywords: | needs-qa | ||||||||||||||
Version: | Latest | Flags: | cyberbotx:
maintainer-feedback+
cyberbotx: maintainer-feedback+ |
||||||||||||||
Hardware: | i386 | ||||||||||||||||
OS: | Any | ||||||||||||||||
Attachments: |
|
I have been getting fallout messages about this already, but I really don't know what I could do about it. For one, this is on HEAD and I don't have a HEAD system at all so I can't get a full log, plus I don't know how stable HEAD is for this sort of thing. For two, this seems like something that should go to the developers of fontforge and not me. I can try and see if this happens with a 10-i386 system as well, but if it doesn't, then I still won't know how to handle this. CC last committer in case they can help Well, I can tell you guys this, it doesn't fail to build in a 10-i386 poudriere jail, so the problem appears to be specific to HEAD-i386. After: 1. upgrade poudriere jails to snapshots from date 02.11.2015; 2. removed all options where they are OpenMP; 3. deleted in poudriere all the old packages; 4. rebuilt the entire repository. problem is not reproduce. conclusion: port option OpenMP - evil. Thanks. Created attachment 162800 [details]
print/fontforge_i386.log
Unfortunately the problem reproduced. CC dim@. Usually you should collect the files failure log mentions (preprocessed source and build script) and submit them to clang bugzilla. (In reply to Dmitry Marakasov from comment #7) Alas, I can not intercept these files in the build in poudriere /tmp/splineutil2-2024cd.c /tmp/splineutil2-2024cd.sh poudriere testport -i Yes, I reported this problem upstream a long time ago: https://llvm.org/bugs/show_bug.cgi?id=21903 For some reason, this bug did not get much traction, and it is still open after almost a year. Currently, I have no ETA on when this gets fixed. Created attachment 162823 [details]
splineutil2-xxxxxx.c.bz2
Created attachment 162824 [details]
splineutil2-xxxxxx.sh
(In reply to Dmitry Marakasov from comment #9) Thanks! clang36 (and llvm36) builds fontforge fine on head/i386. So, the workaround may be to build with it on head/i386. Created attachment 169350 [details]
Diff to Makefile of print/fontforge
Created attachment 169352 [details]
poudriere log for i386 head (as of r297216)
I proposed a workaround to use clang36 instead of clang37 or clang38 on i386. How about this workaround? I suppose if the patch works, I'm fine with it. A commit references this bug: Author: mandree Date: Thu May 26 21:57:29 UTC 2016 New revision: 415915 URL: https://svnweb.freebsd.org/changeset/ports/415915 Log: Fix build on HEAD-i386, using clang 3.6, not newer. PR: 204175 Submitted by: Hiroo Ono Reported by: Ivan Klymenko Approved by: Naram Qashat (maintainer) Changes: head/print/fontforge/Makefile |
Created attachment 162634 [details] fontforge-i386.log