[PATCH] configure: add a fallback check for zlib

Since zlib is part of the base system, FreeBSD chose not to register it in pkg-config through zlib.pc. As a fallback test, configure will build and run a zlib version check and make sure the header and library versions are compatible. --- compat/have_zlib.c | 6 ++ configure | 21

[PATCH] configure: add a fallback check for zlib

Since zlib is part of the base system, FreeBSD chose not to register it in pkg-config through zlib.pc. As a fallback test, configure will build and run a zlib version check and make sure the header and library versions are compatible. --- compat/have_zlib.c | 6 ++ configure | 21

[PATCH 1/2] configure: add a fallback check for zlib

Since zlib is part of the base system, FreeBSD chose not to register it in pkg-config through zlib.pc. As a fallback test, configure will build and run a zlib version check and make sure the header and library versions are compatible. --- compat/have_zlib.c | 6 ++ configure | 21

[PATCH] Fallback check for zlib.

--- compat/have_zlib.c | 6 ++ configure | 21 - 2 files changed, 22 insertions(+), 5 deletions(-) create mode 100644 compat/have_zlib.c diff --git a/compat/have_zlib.c b/compat/have_zlib.c new file mode 100644 index 000..998c697 --- /dev/null +++

[PATCH] Fallback check for zlib

Added the fallback check for zlib. Tested on FreeBSD stable/10. C test checks for major zlib compatibility (see zlib doc/examples). X?c? (1): Fallback check for zlib. compat/have_zlib.c | 6 ++ configure | 21 - 2 files changed, 22 insertions(+), 5

pkg-config zlib check in 3c13bc

On Sat, May 10, 2014 at 09:46:00AM +0900, David Bremner wrote: > > int main(void) > > { > > return(ZLIB_VERNUM >= 0x1252); > > } > > OK, that sounds like it could work. Ideally, somebody on FreeBSD could > check... > > d Such check will work on FreeBSD, and would be great! As a side note,

Re: pkg-config zlib check in 3c13bc

On Sat, May 10, 2014 at 09:46:00AM +0900, David Bremner wrote: int main(void) { return(ZLIB_VERNUM = 0x1252); } OK, that sounds like it could work. Ideally, somebody on FreeBSD could check... d Such check will work on FreeBSD, and would be great! As a side note, is there any

[PATCH] Fallback check for zlib

Added the fallback check for zlib. Tested on FreeBSD stable/10. C test checks for major zlib compatibility (see zlib doc/examples). Xīcò (1): Fallback check for zlib. compat/have_zlib.c | 6 ++ configure | 21 - 2 files changed, 22 insertions(+), 5 deletions

[PATCH] Fallback check for zlib.

--- compat/have_zlib.c | 6 ++ configure | 21 - 2 files changed, 22 insertions(+), 5 deletions(-) create mode 100644 compat/have_zlib.c diff --git a/compat/have_zlib.c b/compat/have_zlib.c new file mode 100644 index 000..998c697 --- /dev/null +++

Linux-only fdatasync() in 3c13bc

Also, commit 3c13bc introduced a call to fdatasync() which is not available on FreeBSD, and probably not either on MacOS at least. Best, -- X?c? -- next part -- A non-text attachment was scrubbed... Name: 0002-Compatibility-for-Linux-s-fdatasync.patch Type: text/x-diff

pkg-config zlib check in 3c13bc

Dear notmuch, Although notmuch was configuring fine on FreeBSD before 3c13bc, the pkg-config check introduced for zlib does not work. Indeed, zlib is part of the base system, and always assumed to be present. Proposed patch puts platform test before pkg-config checks, and add a special case for

pkg-config zlib check in 3c13bc

for zlib on FreeBSD. uname -U is used to get (numeric) OS version, and compared to lowest release where at least zlib 1.2.5.2 was available (that’s FreeBSD 9.1, with zlib 1.2.7). Best, -- Xīcò From ca0b168ac01391b4137de504bea2845d39d0fff9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?X=C4=ABc=C3=B2?= x

Linux-only fdatasync() in 3c13bc

Also, commit 3c13bc introduced a call to fdatasync() which is not available on FreeBSD, and probably not either on MacOS at least. Best, -- Xīcò From e2b9520e69e52b35348d07eb53a6a88d1397fa3f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?X=C4=ABc=C3=B2?= x...@atelo.org Date: Tue, 6 May 2014 12:56:03