> On Jul 3, 2017, at 14:46, Kurt Jaeger wrote:
>
> Use __FreeBSD_version from sys/param.h:
>
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/versions.html
Thanks. That looks great. Also, for my specific case of the addition of
clock_nanosleep(), it looks from time.h l
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #44 from Cassiano Peixoto ---
(In reply to Mateusz Guzik from comment #43)
Ok patch applied. I'll let you know the results.
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #43 from Mateusz Guzik ---
Yes, apply the patch to a clean tree. Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org ma
I've had a kernel crash with 3 different RC1 kernels.
kernel: FreeBSD 11.1-RC1 #71 r313908+b08656c3ba28(releng/11.1): Sun Jul 2
23:15:23 PDT 2017
kernel: FreeBSD 11.1-RC1 #72 r313908+64e0abde4c70(releng/11.1): Mon Jul 3
07:43:42 PDT 2017
kernel: FreeBSD 11.1-RC1 #73 r313908+ff3a058c4f83(releng
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #42 from Cassiano Peixoto ---
(In reply to Mateusz Guzik from comment #41)
Ok you are right. I reverted all files touched by previous patch. Am i right?
And then should i apply only this last patch?
--
You are receiving this m
Hi!
> Some time ago, I ported a linux program that was using clock_nanosleep().
> I see now that the extra code I'd put in isn't needed anymore in 11-stable,
> as it appears this call was added in 11.1. My question is, to
> properly protect these changes, what is the best way to know at
> compi
Some time ago, I ported a linux program that was using clock_nanosleep(). I
see now that the extra code I’d put in isn’t needed anymore in 11-stable, as it
appears this call was added in 11.1. My question is, to properly protect these
changes, what is the best way to know at compile time, e
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #41 from Mateusz Guzik ---
This looks like leftovers from the previous patch. Just restore the original
state of the tree and patch that.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #40 from Cassiano Peixoto ---
(In reply to Mateusz Guzik from comment #39)
Mateusz,
I can test it, but my 10-STABLE version has a different code:
/* Release a write lock. */
#define __rw_wunlock(rw, tid, file, line) do {
