[283136]: buildworld failure: usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lproc

Current sources (r283136) die on buildworld with the following error: [...] --- cddl/lib__L --- /usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lproc cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [libdtrace.so.2] Error code 1 ___

Build failed in Jenkins: FreeBSD_HEAD_i386 #160

See Changes: [hiren] Add a new sysctl net.inet.tcp.hostcache.purgenow=1 to expire and purge all entries in hostcache immediately. In collaboration with: bz, rwatson MFC after: 1 week Relnotes: yes Sponsored by: Limeli

Build failed in Jenkins: FreeBSD_HEAD-tests2 #1043

See -- Started by upstream project "Build_Image_and_Run_Tests_in_Bhyve_HEAD" build number 1089 originally caused by: Started by upstream project "FreeBSD_HEAD" build number 2777 originally caused

Build failed in Jenkins: FreeBSD_HEAD_i386 #159

See Changes: [bapt] Reduce overlinking. Because of libdtrace there is still a bit a overlinking but nothing we can deal with easily [bapt] Correctly link libdtrace and convert to LIBADD Make dtrace only link to libdtrace [bapt] Fix

Re: pedantic compiler warnings: double semicolons, function to data pointers

On 05/19/2015 14:42, Luigi Rizzo wrote: > While trying to compile some of my (kernel) code in different environments, > i noticed a couple of errors that perhaps might be worth fixing > > - extra semicolons. These come either from explicit repetitions in the code > (see the output of a grep at th

Re: pedantic compiler warnings: double semicolons, function to data pointers

On Tue, 2015-05-19 at 11:56 -0700, Adrian Chadd wrote: > On 19 May 2015 at 11:42, Luigi Rizzo wrote: > > While trying to compile some of my (kernel) code in different environments, > > i noticed a couple of errors that perhaps might be worth fixing > > > > - extra semicolons. These come either fro

Re: pedantic compiler warnings: double semicolons, function to data pointers

On 19 May 2015 at 11:42, Luigi Rizzo wrote: > While trying to compile some of my (kernel) code in different environments, > i noticed a couple of errors that perhaps might be worth fixing > > - extra semicolons. These come either from explicit repetitions in the code > (see the output of a grep

pedantic compiler warnings: double semicolons, function to data pointers

While trying to compile some of my (kernel) code in different environments, i noticed a couple of errors that perhaps might be worth fixing - extra semicolons. These come either from explicit repetitions in the code (see the output of a grep at the end of this message), or sometimes from the e

Re: [RFC] Replace gnu groff in base by heirloom doctools

Hello, Baptiste Daroussin wrote: |On Tue, May 19, 2015 at 02:37:22PM +0200, Steffen Nurpmeso wrote: |> Baptiste Daroussin wrote: |>|On Sat, May 16, 2015 at 01:42:26AM +0200, Julian H. Stacey wrote: |> |>|>> I think keeping a fully functionnal roff(7) toolchain part of the |>|>> base syste

Re: [RFC] Replace gnu groff in base by heirloom doctools

On Tue, May 19, 2015 at 06:52:40PM +0200, Steffen Nurpmeso wrote: > Hello, > > Baptiste Daroussin wrote: > |On Tue, May 19, 2015 at 02:37:22PM +0200, Steffen Nurpmeso wrote: > |> Baptiste Daroussin wrote: > |>|On Sat, May 16, 2015 at 01:42:26AM +0200, Julian H. Stacey wrote: > |> > |>|>> I

Build failed in Jenkins: FreeBSD_HEAD-tests2 #1042

See -- Started by upstream project "Build_Image_and_Run_Tests_in_Bhyve_HEAD" build number 1088 originally caused by: Started by upstream project "FreeBSD_HEAD" build number 2776 originally caused

Re: [RFC] Replace gnu groff in base by heirloom doctools

On Tue, May 19, 2015 at 02:37:22PM +0200, Steffen Nurpmeso wrote: > Baptiste Daroussin wrote: > |On Sat, May 16, 2015 at 01:42:26AM +0200, Julian H. Stacey wrote: > > |>> I think keeping a fully functionnal roff(7) toolchain part of the > |>> base system is very good on a unix. > > |>> From

Re: [RFC] Replace gnu groff in base by heirloom doctools

Baptiste Daroussin wrote: |On Sat, May 16, 2015 at 01:42:26AM +0200, Julian H. Stacey wrote: |>> I think keeping a fully functionnal roff(7) toolchain part of the |>> base system is very good on a unix. |>> From what I could check I cannot find any regression when \ |>> migrating from gnu

Aw: Re: [RFC] Replace gnu groff in base by heirloom doctools

Steffen Nurpmeso wrote: > It seems you haven't checked at all. > It seems to me that e.g. mdoc(7) of n-t-r seems to require quite > a bit of work in order to be at all usable. This is not completely true. It is usable, I did check it with all about 7000 manpages in the base of OpenBSD. But it d

Re: [RFC] Replace gnu groff in base by heirloom doctools

On Sat, May 16, 2015 at 01:42:26AM +0200, Julian H. Stacey wrote: > Hi Bapt & current@ > > > I think keeping a fully functionnal roff(7) toolchain part of the > > base system is very good on a unix. > > Yes, Unix has always also been a tool to get jobs done (aka PWB), > as well as merely recompil

Re: ixl and BOOTP

On 2015-5-18, at 19:22, Ryan Stone wrote: > Hm, I'm unable to reproduce this on the latest -CURRENT (r283059). My > hardware is a little different from yours -- my CPU is a Haswell Xeon, and I > have only 1 igb port and no ixgbe. Also, I was just booting GENERIC. I > didn't have Xen or anyth