ports broken in current

2014-05-07 Thread Shane Ambler
I have just updated my 11-CURRENT tinderbox machine and found an issue that breaks ports building. make: "/usr/share/mk/bsd.port.mk" line 15: Could not find bsd.own.mk This is highlighted as tinderbox creates a clean build environment while the base system kept working with the old file being lef

Re: New and exciting panic, possibly re(4)

2014-05-07 Thread Sean Bruno
On Wed, 2014-05-07 at 12:24 -0700, Sean Bruno wrote: > While screwing around with comcast, I can trivially get this panic out > of my desktop machine, and am very confused. It seems to happen on link > change up/down events. I'm running 11.0-CURRENT FreeBSD 11.0-CURRENT #5 > r265280M. I don't ha

Re: devel/qmake4: "/usr/share/mk/bsd.prog.mk" line 176: Malformed conditional (${COMPILER_TYPE}

2014-05-07 Thread Warner Losh
On May 6, 2014, at 9:38 AM, O. Hartmann wrote: > > On CURRENT (FreeBSD 11.0-CURRENT #0 r265433: Tue May 6 13:37:15 CEST 2014 > amd64) the > build/updating of port devel/qmake4 fails due to: > > ===> Building for qt4-qmake-4.8.6 > make[1]: "/usr/share/mk/bsd.prog.mk" line 176: Malformed cond

New and exciting panic, possibly re(4)

2014-05-07 Thread Sean Bruno
While screwing around with comcast, I can trivially get this panic out of my desktop machine, and am very confused. It seems to happen on link change up/down events. I'm running 11.0-CURRENT FreeBSD 11.0-CURRENT #5 r265280M. I don't have any direct evidence that this is re(4), just a hunch from

/usr/src: svn status: svn: E200030: sqlite[S1]: near "1": syntax error

2014-05-07 Thread O. Hartmann
I get this weird error in /usr/src with the port devel/subversion: root@thor: [ports] svn st svn: E200030: sqlite[S1]: near "1": syntax error Using /bin/svn everything is clear. What happened here? OS is FreeBSD 11.0-CURRENT #0 r265433: Tue May 6 13:37:15 CEST 2014 amd64 Regards, Oliver

Fwd: New /dev/random code for review please.

2014-05-07 Thread Mark R V Murray
Hi Folks, Please could the wisdom-of-crowds apply its collective attention to this? Thanks! M Begin forwarded message: > From: Mark R V Murray > Subject: New /dev/random code for review please. > Date: 4 May 2014 18:28:43 BST > To: "sect...@freebsd.org Team" > Content-Type: multipart/signed;

Re: wbem, cim and instrumentation

2014-05-07 Thread Kurt Jaeger
Hi! > One thing I feel FreeBSD always ignored  is instrumentation frameworks. > I am talking about wbem, cim model and implementation like OpenPegasus. Why > is that? > I ported OpenPegasus to work in FreeBSD with few patches. > github.com/brunolauze/openpegasus-providers > > my openpegasus por

Re: wbem, cim and instrumentation

2014-05-07 Thread Sean Bruno
On Wed, 2014-05-07 at 08:39 -0400, Bruno Lauzé wrote: > One thing I feel FreeBSD always ignored is instrumentation frameworks. > I am talking about wbem, cim model and implementation like OpenPegasus. Why > is that? > I ported OpenPegasus to work in FreeBSD with few patches. > However, of course

wbem, cim and instrumentation

2014-05-07 Thread Bruno Lauzé
One thing I feel FreeBSD always ignored  is instrumentation frameworks. I am talking about wbem, cim model and implementation like OpenPegasus. Why is that? I ported OpenPegasus to work in FreeBSD with few patches. However, of course without providers a wbem doesn't go far. I started to see how t

Re: MFC of Revision 261913

2014-05-07 Thread Dag-Erling Smørgrav
Oliver Pinter writes: > Can you merge back the r261913 commit to stable/10 or is this a POLA > violation? It needs to be accompanied by r264964, and you should ask jmg@ about merging r262945 and r263218 as well. DES -- Dag-Erling Smørgrav - d...@des.no __