FreeBSD ports you maintain which are out of date

2017-08-15 Thread portscout
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

[Bug 221311] [NEW PORT] databases/influxdb-python: InfluxDB Python client

2017-08-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221311 Konstantin Shapkin changed: What|Removed |Added Attachment #185152|0 |1 is obsolete|

[Bug 220484] math/py-numpy: fails to build 11.0 aarch64 due to clang crash (196 ports skipped)

2017-08-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220484 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #8 from

[Bug 220484] math/py-numpy: fails to build 11.0 aarch64 due to clang crash (196 ports skipped)

2017-08-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220484 --- Comment #9 from Andrew Turner --- (In reply to Ed Maste from comment #8) The main reason to support 11.0 with arm64 is that's what portmgr targets when building packages. -- You are receiving this mail because: You are the assignee fo

[Bug 220484] math/py-numpy: fails to build 11.0 aarch64 due to clang crash (196 ports skipped)

2017-08-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220484 --- Comment #10 from Ed Maste --- (In reply to Andrew Turner from comment #9) Ah yes, good point. Perhaps setting USES=compiler:c++14-lang for arm64 could be a suitable workaround? -- You are receiving this mail because: You are the assig