Re: kldref: unhandled relocation type 2

2018-08-18 Thread Dimitry Andric
On 18 Aug 2018, at 00:50, Steve Kargl wrote: > > On Fri, Aug 17, 2018 at 05:50:06PM -0400, Ed Maste wrote: >> On 8 August 2018 at 13:27, Warner Losh wrote: >>> % /usr/obj/usr/src/i386.i386/usr.sbin/kldxref/kldxref /boot/kernel kldxref: unhandled relocation type 2 (40+ messages...

Re: awk manual is outdated

2018-08-18 Thread Mateusz Piotrowski
On Tue, 24 Jul 2018 01:06:19 +0200 Samy Mahmoudi wrote: >The awk manual seems out of date. > >For example, the -V option is documented but is unknown at execution. >Reciprocally, --version is not documented but is functional at execution. >Under FreeBSD 12.0-CURRENT, the date at the end of the ma

Fwd: Warnings about dlclose before thread exit. __cxa_thread_call_dtors

2018-08-18 Thread Willem Jan Withagen
Hi, I've sent the question below to the Ceph-devel list, asking if any recent changes would be able to cause this. But then of course this could stem from FreeBSD libs, and of ports So the question here is if anybody has gotten these "warnings" in other tools. --WjW Forwarded

Executables with [ -def __linux__ ]

2018-08-18 Thread blubee blubeeme
This is going out to both current and ports in hopes someone can offer some guidance on this issue. I'm porting some code that seems to want to have -def __linux__ when I run the executable with verbose output, take a look below -- -opt

Sharing compiled builds between multiple 12-CURRENT boxes.

2018-08-18 Thread Dhananjay Balan
Hi, I run 12-CURRENT on few machines, some more powerful that other (all of them x86_64, march varies). Is there is a way to avoid building CURRENT on all machines? Rather than building everywhere, can I just build it on the big server that I have and copy and update my laptop? - Dhananjay Bala

Re: Sharing compiled builds between multiple 12-CURRENT boxes.

2018-08-18 Thread Cy Schubert
In message <20180818223420.rjisst4vuxzxbcrl@kazhap>, Dhananjay Balan writes: > Hi, > > I run 12-CURRENT on few machines, some more powerful that other (all > of them x86_64, march varies). > > Is there is a way to avoid building CURRENT on all machines? Rather > than building everywhere, can I ju

Re: Sharing compiled builds between multiple 12-CURRENT boxes.

2018-08-18 Thread David Wolfskill
On Sun, Aug 19, 2018 at 12:34:20AM +0200, Dhananjay Balan wrote: > Hi, > > I run 12-CURRENT on few machines, some more powerful that other (all > of them x86_64, march varies). > > Is there is a way to avoid building CURRENT on all machines? Rather > than building everywhere, can I just build it

Re: Sharing compiled builds between multiple 12-CURRENT boxes.

2018-08-18 Thread Mike Appleby
On Sat, Aug 18, 2018 at 5:34 PM, Dhananjay Balan wrote: > Hi, > > I run 12-CURRENT on few machines, some more powerful that other (all > of them x86_64, march varies). > > Is there is a way to avoid building CURRENT on all machines? Rather > than building everywhere, can I just build it on the big

Re: Sharing compiled builds between multiple 12-CURRENT boxes.

2018-08-18 Thread Shane Ambler
On 19/8/18 8:04 am, Dhananjay Balan wrote: > Hi, > > I run 12-CURRENT on few machines, some more powerful that other (all > of them x86_64, march varies). > > Is there is a way to avoid building CURRENT on all machines? Rather > than building everywhere, can I just build it on the big server tha

Re: kernel build failure

2018-08-18 Thread John Baldwin
On 8/14/18 1:35 AM, Matthew Macy wrote: > On Mon, Aug 13, 2018 at 5:33 PM Rick Macklem wrote: > >> Rodney W. Grimes wrote: On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > Sorry guys, last time I touched ZFS I tried to push to make it an >> option to > statically link and w