[Bug 227698] www/iridium, www/qt5-webengine: clang 6.0 crashes during build
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227698 --- Comment #10 from commit-h...@freebsd.org --- A commit references this bug: Author: dim Date: Mon Apr 23 23:07:58 UTC 2018 New revision: 332898 URL: https://svnweb.freebsd.org/changeset/base/332898 Log: Pull in r329771 from upstream llvm trunk (by Craig Topper): [X86] In X86FlagsCopyLowering, when rewriting a memory setcc we need to emit an explicit MOV8mr instruction. Previously the code only knew how to handle setcc to a register. This should fix a crash in the chromium build. This fixes various assertion failures while building ports targeting i386: * www/firefox: isReg() && "This is not a register operand!" * www/iridium, www/qt5-webengine: (I.atEnd() || std::next(I) == def_instr_end()) && "getVRegDef assumes a single definition or no definition" * devel/powerpc64-gcc: FromReg != ToReg && "Cannot replace a reg with itself" Reported by: jbeich PR: 225330, 227686, 227698, 227699 MFC after:1 week X-MFC-With: r332833 Changes: head/contrib/llvm/lib/Target/X86/X86FlagsCopyLowering.cpp -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 227683] www/chromium, www/iridium, www/qt5-webengine: switch to llvm60
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227683 --- Comment #2 from Carlos J. Puga Medina--- I hope to do some tests during the weekend. Thanks Jan :) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 227683] www/chromium, www/iridium, www/qt5-webengine: switch to llvm60
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227683 Carlos J. Puga Medinachanged: What|Removed |Added Status|New |Open -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 227698] www/iridium, www/qt5-webengine: clang 6.0 crashes during build
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227698 Carlos J. Puga Medinachanged: What|Removed |Added CC||c...@freebsd.org --- Comment #9 from Carlos J. Puga Medina --- Iridium can be updated to 2017.11 (based on the Chromium version 62.0.3202.94), but I will need some time to update the port or more manpower to achieve this goal before. Anyway I just realized that the Iridium developers are working on 65.x release http://lists.inai.de/pipermail/iridium/2018-April/000725.html -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 227683] www/chromium, www/iridium, www/qt5-webengine: switch to llvm60
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227683 Carlos J. Puga Medinachanged: What|Removed |Added CC||c...@freebsd.org Assignee|ports-b...@freebsd.org |c...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug.
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/k...@freebsd.org.html Port| Current version | New version +-+ deskutils/latte-dock| 0.7.4 | 0.7.5 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks.
[Bug 227428] devel/cmake: fails to find suffixed libboost_python
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227428 --- Comment #18 from Willem Jan Withagen--- (In reply to Willem Jan Withagen from comment #17) Yesterday I had some time to work a bit on this, and with boost 1.67 and CMake 3.11.0_2 I was able to build and test correctly. This was using a default environment based on python 2.7, even though Ceph starts to move to python3. (I have both installed) So a challenge might be to have a poudriere env that will be able to have both python 2.7 AND python3? As I have the feeling that this is not really what the ports team is aiming for? -- You are receiving this mail because: You are on the CC list for the bug.