Re: default named.conf in bind ports and slaving from f-root

2017-04-15 Thread Kevin Oberman
On Sat, Apr 15, 2017 at 7:02 PM, George Mitchell wrote: > On 04/14/17 08:37, Thomas Steen Rasmussen wrote: > > Hello, > > > > Cloudflare deployed a bunch (74 apparently) of new f-root dns > > servers, which do not permit AXFR like the other f-root instances > > do. > >

Re: default named.conf in bind ports and slaving from f-root

2017-04-15 Thread George Mitchell
On 04/14/17 08:37, Thomas Steen Rasmussen wrote: > Hello, > > Cloudflare deployed a bunch (74 apparently) of new f-root dns > servers, which do not permit AXFR like the other f-root instances > do. > [...] > A good alternative could be to change named.conf to use > lax.xfr.dns.icann.org and

Re: FreeBSD Port: graphics/opencv -- Fails to compile

2017-04-15 Thread Kevin Oberman
On Sat, Apr 15, 2017 at 3:09 PM, Peter Smith wrote: > I am running > > # uname -a > > FreeBSD red 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22 > > 06:12:04 UTC 2017 r...@amd64-builder.daemonology.net:/usr/obj/usr/ > src/sys/GENERIC > > amd64 > > > > > Having

FreeBSD Port: graphics/opencv -- Fails to compile

2017-04-15 Thread Peter Smith
I am running # uname -a > FreeBSD red 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22 > 06:12:04 UTC 2017 > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > amd64 > Having just refreshed my ports tree (portsnap fetch, etc), I'm rebuilding all my installed ports

Re: LLVM port(s) take very long time to package

2017-04-15 Thread Alexey Dokuchaev
On Fri, Apr 14, 2017 at 04:42:35PM +0200, Michael Gmelin wrote: > > On 14. Apr 2017, at 16:22, Alexey Dokuchaev wrote: > > On Wed, Apr 12, 2017 at 12:06:42PM +0200, Michael Gmelin wrote: > >>> On 12. Apr 2017, at 11:37, Alexey Dokuchaev wrote: > >>> ... >

Re: default named.conf in bind ports and slaving from f-root

2017-04-15 Thread Bob Willcox
On Fri, Apr 14, 2017 at 05:25:21PM +0200, Thomas Steen Rasmussen wrote: > On 04/14/2017 04:51 PM, Mathieu Arnold wrote: > > Hi, > > > > I'm busy right now, could you open a PR so that I don't loose and forget > > this ? > > Sure thing, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218656 > >

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-04-15 Thread Alexey Dokuchaev
Sorry Matthew, forgot to reply to this one. On Wed, Apr 05, 2017 at 07:01:35PM +0200, Matthew Rezny wrote: > On Wednesday 05 April 2017 16:15:41 Alexey Dokuchaev wrote: > > ... > > Hmm, I don't quite get it: shouldn't static linking actually increase > > the binaries (and thus the package) size?

Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)

2017-04-15 Thread Mark Linimon
On Fri, Apr 14, 2017 at 08:27:29PM -0700, Mark Millard wrote: > I've seen material quoted from a exp-run that reported > that about 54(?) ports were then blocked by lang/gcc6-aux > not building. Although the first is an older run (the last complete run IIUC), there were 50 and 51 respectively as

RELRO breaks net/openmpi, was: net/openmpi fails to compile with default settings

2017-04-15 Thread Grzegorz Junka
Thanks Anton, The compilation was broken because of OPTIONS_FILE_SET+=RELRO in devel/binutils After disabling RELRO net/openmpi can be compiled successfully. Not sure if this is a bug or expected behaviour. Regards Grzegorz On 14/04/2017 11:26, Anton Shterenlikht wrote: I don't know

FreeBSD ports you maintain which are out of date

2017-04-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,

Re: graphics/opencv2 orphaned. Where from here

2017-04-15 Thread Herbert J. Skuhra
Rainer Hurling skrev: > > Am 15.04.2017 um 01:04 schrieb Kevin Oberman: >> Thanks for the work on opencv, but PLEASE put something in UPDATING when >> you make changes that impact large numbers of ports. I see opencv2 as >> orphaned, so I can't stay there. >> >> Do I reset the origin of opencv2

Re: graphics/opencv2 orphaned. Where from here

2017-04-15 Thread Rainer Hurling
Am 15.04.2017 um 01:04 schrieb Kevin Oberman: > Thanks for the work on opencv, but PLEASE put something in UPDATING when > you make changes that impact large numbers of ports. I see opencv2 as > orphaned, so I can't stay there. > > Do I reset the origin of opencv2 to opencv? Or will I need to