---
Makefile | 4 ++--
config.mk | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Makefile b/Makefile
index 2bea555..d53171c 100644
--- a/Makefile
+++ b/Makefile
@@ -40,8 +40,8 @@ install: all
@echo installing executable file to ${DESTDIR}${PREFIX}/bin
@mkd
Bump. The unpatched code doesn't work properly on BSD for reasons not
obvious to the person compiling it.
On Mon, Apr 28, 2014 at 10:46 AM, Steve Dee wrote:
>
> ---
> Makefile | 4 ++--
> config.mk | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
&g
See also: https://kentonv.github.io/capnproto/
On Tue, Jul 1, 2014 at 8:01 AM, Markus Teich wrote:
> Rob wrote:
>> You've got alignment issues here - msg will be aligned to support any
>> type (as malloc's interface specifies) so msg+1 will most likely be on
>> an odd address, one byte off a highly aligned address. This means if
>> your struct
OpenBSD doesn't have utmpx.h or clearenv. Also, the dependency
"$(BIN): util.a" seems to shadow the implicit build rule in BSD make,
resulting in nothing past util.a getting built. The patch includes a
rather stupid workaround for this. (Less stupid solutions welcome ---
it'd be simple to specify w
On Fri, Jul 12, 2013 at 5:36 PM, Galos, David
wrote:
>> OpenBSD doesn't have utmpx.h or clearenv.
> Does it also not have "getutent"?
It doesn't, as far as I can tell. That implementation comes from OpenBSD's who.
On Thu, Jul 18, 2013 at 11:31 AM, Galos, David
wrote:
>> It doesn't, as far as I can tell. That implementation comes from OpenBSD's
>> who.
> Is the utmp file guaranteed to be machine endian?
OpenBSD assumes it is. And on Linux, man 5 utmp claims: "The file
format is machine-dependent, so it is r
BSD-compatible, opinionated df attached. Always prints 512-blocks.
Guesses high on used counts. Untested in Linux because time.
The -std=c99 patch is to suppress warnings about using the %llu format
specifier. It's kept separate in case C99 is undesirable, though.
On Mon, Jul 22, 2013 at 9:55 AM,
C-[hjkl] are in-page scrolling. C-i and C-o are back/forth page
navigation, just like in Vim. This frees up C-u for view source, just
like in Chrome. This patch messes with surfers' muscle memory, but I
think the consistency with the rest of the world is nice enough to at
least be worth an email. D
Accompanying manual patch.
On Mon, Jul 22, 2013 at 11:33 AM, Steve Dee wrote:
> C-[hjkl] are in-page scrolling. C-i and C-o are back/forth page
> navigation, just like in Vim. This frees up C-u for view source, just
> like in Chrome. This patch messes with surfers' muscle memory,
Nice.
BSD doesn't have mntent or /proc, but does have getmntinfo. I think we
can create a common interface that requires a minimal amount of
conditional compilation (though obviously no conditional compilation
is better than any conditional compilation), but I don't have time to
do this for the ne
On Tue, Jul 23, 2013 at 10:29 AM, sin wrote:
> On Tue, Jul 23, 2013 at 10:18:01AM -0400, Steve Dee wrote:
>> I don't have time to do this for the next few days.
Actually, I had a bit of time before running off into the woods.
Here's something that compiles on both Ope
soup_message_get_flags returns a bunch of flags besides
SOUP_MESSAGE_CERTIFICATE_TRUSTED, so the XOR check was incorrect.
While I was tracking this bug, I switched from libsoup's deprecated [0]
ssl-ca-file to its non-deprecated tls-database property. I don't know if I
did that properly, having nev
13 matches
Mail list logo
