second call for 2016Q4 status reports

2016-12-26 Thread Benjamin Kaduk
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is January 7, 2016, for work done in October through December. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great w

Mozilla firefox freezes/zombie on FreeBSD current

2016-12-26 Thread Subbsd
Hi, On recent FreeBSD version (tested on two host: one from svn://svn.freebsd.org/base/head ( r310507 now) and second from https://github.com/FreeBSDDesktop/freebsd-base-graphics.git / drm-next-4.7 ) and latest firefox ( firefox-50.1.0_4,1 ) I often get into a situation where firefox is hands. It

Re: pkg on old current - library woes

2016-12-26 Thread Jeffrey Bouquet
On Mon, 26 Dec 2016 17:27:06 +0100, Marc UBM Bocklet wrote: > > Hi list, > > I'm writing this as an reminder for others who might be in a similar > situation. Don't blindly (like me) use pkg on an old current or you'll > (understandably) run into tons of library / linking issues. > > I upda

CURRENT: arm64 buildworld failure: numa_setaffinity.pico: In function `numa_setaffinity':

2016-12-26 Thread O. Hartmann
Trying to build AARCH64 world on amd64 box running most recent CURRENT (FreeBSD 12.0-CURRENT #23 r310556: Sun Dec 25 21:45:35 CET 2016 amd64), sources are r310603. port devel/aarch64-binutils is installed as requested, the environment has been setup using setenv MAKEOBJDIRPREFIX /pool/sources/C

CURRENT: ARM64 support: Odroid-C2

2016-12-26 Thread O. Hartmann
I have a quick question about using FreeBSD 12-CURRENT on an Odroid-C2 SoC. I tried the most recent image found on the repository provided by FreeBSD.org, but neither on SD card nor on USB drive the image boots. I just dd'd the image to the appropriate memory device, so I didn't investigate much

Re: A quick question

2016-12-26 Thread blubee blubeeme
Thanks for the follow-up. On Sat, Dec 24, 2016, 17:08 Dave Cottlehuber wrote: > On Wed, 21 Dec 2016, at 06:39, blubee blubeeme wrote: > > Can I bump this issue one more time? > > > > On Sun, Dec 18, 2016, 18:38 Dave Cottlehuber wrote: > > > > > On Sun, 18 Dec 2016, at 10:07, blubee blubeeme wro