Re: reducing build times; selecting specific clang targets

2017-12-08 Thread Ed Schouten
Hi Michael, 2017-12-09 4:57 GMT+01:00 Michael Butler : > As clang builds for multiple targets unconditionally, it takes *days* to > build on one of my devices (700MHz Pentium-3). > > Is there a way to restrict the build targets to i386 only? If not, can we > implement

reducing build times; selecting specific clang targets

2017-12-08 Thread Michael Butler
As clang builds for multiple targets unconditionally, it takes *days* to build on one of my devices (700MHz Pentium-3). Is there a way to restrict the build targets to i386 only? If not, can we implement one? imb ___

Re: GPTZFSBOOT in Current r326622 has problems

2017-12-08 Thread Warner Losh
On Fri, Dec 8, 2017 at 7:31 PM, Thomas Laus wrote: > Warner Losh [i...@bsdimp.com] wrote: > > Looks like -DEFI_ZFS_BOOT was dropped from boot1.c in r326589. I've > fixed > > it in r326714. > > > Warren: > > I just completed a buildworld on r326720 and it failed to boot again >

Re: GPTZFSBOOT in Current r326622 has problems

2017-12-08 Thread Thomas Laus
Warner Losh [i...@bsdimp.com] wrote: > Looks like -DEFI_ZFS_BOOT was dropped from boot1.c in r326589. I've fixed > it in r326714. > Warren: I just completed a buildworld on r326720 and it failed to boot again with a hex dump and BTX failure. I can take a photograph and post it somewhere of the

[PATCH] Document powl and tgammal kludges

2017-12-08 Thread Steve Kargl
The following patch documents the remaining kludges that theraven@ committed in r255294 on 2013-09-06. I have cleaned up all of the others, but powl and tgammal remain. ngie@ seems to have documented the existence of powl with r290605, but did not document the rather poor numerical accuracy of

Re: GPTZFSBOOT in Current r326622 has problems

2017-12-08 Thread Warner Losh
Looks like -DEFI_ZFS_BOOT was dropped from boot1.c in r326589. I've fixed it in r326714. Warner On Thu, Dec 7, 2017 at 5:44 AM, Thomas Laus wrote: > On 12/06/17 19:38, Warner Losh wrote: > > > > OK. Still a fair number of changes, including changes to geli to fix > >

Re: Breakage with sys.kern.ptrace_test.{ptrace__parent_sees_exit_after_child_debugger, parent_sees_exit_after_unrelated_debugger} after r325719:325721

2017-12-08 Thread Mark Johnston
On Thu, Nov 16, 2017 at 09:07:56AM -0800, Ngie Cooper (yaneurabeya) wrote: > Hi Mateusz, > Per Jenkins, these two tests are broken after r325719:325721: > https://ci.freebsd.org/job/FreeBSD-head-amd64-test/4987/ > . > Thanks, >

Re: valloric YCM [header definitions]

2017-12-08 Thread Gary Jennejohn
On Fri, 8 Dec 2017 21:23:04 +0800 blubee blubeeme wrote: > On Wed, Dec 6, 2017 at 2:18 AM, blubee blubeeme wrote: > > > I'm looking for where the u_int, u_long headers are defined? > > These are not headers, they're typedefs. These are defined in

Re: valloric YCM [header definitions]

2017-12-08 Thread Hans Petter Selasky
On 12/08/17 14:23, blubee blubeeme wrote: On Wed, Dec 6, 2017 at 2:18 AM, blubee blubeeme wrote: Hi, These questions are better off at questi...@freebsd.org :-) I'm looking for where the u_int, u_long headers are defined? Anyway, it appears you are having some fun

Re: valloric YCM [header definitions]

2017-12-08 Thread blubee blubeeme
On Wed, Dec 6, 2017 at 2:18 AM, blubee blubeeme wrote: > I'm looking for where the u_int, u_long headers are defined? > > for instance MOD_LOAD, UNLOAD, ENOTSUP along with u_int and u_long aren't > being picked up by libclang > > module_t isn't being found either but I