Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 23551431FAF for ; Thu, 17 Apr 2014 15:52:16 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lhugZWUjWG5R for ; Thu, 17 Apr 2014 15:52:08 -0700 (PDT) Received: from mx.xen14.node3324.gplhost.com (gitolite.debian.net [87.98.215.224]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id CF688431FAE for ; Thu, 17 Apr 2014 15:52:07 -0700 (PDT) Received: from remotemail by mx.xen14.node3324.gplhost.com with local (Exim 4.72) (envelope-from ) id 1Wav8b-0002qy-Oe; Thu, 17 Apr 2014 22:50:33 +0000 Received: (nullmailer pid 1818 invoked by uid 1000); Thu, 17 Apr 2014 22:50:15 -0000 From: David Bremner To: Allan Streib Subject: Re: notmuch, OpenBSD issues In-Reply-To: <871twvokwm.fsf@viking.indiana.edu> References: <871twvokwm.fsf@viking.indiana.edu> User-Agent: Notmuch/0.17+174~g4efbc9f (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Fri, 18 Apr 2014 07:50:15 +0900 Message-ID: <877g6ny3iw.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain Cc: Tomi Ollila , notmuch@notmuchmail.org X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2014 22:52:16 -0000 Allan Streib writes: > Hi David, > > I've been using notmuch on OpenBSD for a while, and I really appreciate > the project. I hope you don't mind my replying to the list. Notmuch is not a one man project... > > In recent days I've had a couple problems building. First issue was a > complaint about "cannonicalize_file_name" being an unknown symbol. I > fixed that with the following: Yeah, that's actually a bug in my fix other fix for openbsd. There's actually a patch queued for merging on the mailing list, see id:1397042643-10975-1-git-send-email-david@tethera.net > The other issue is with the support for gzipped dump and restore; > OpenBSD currently provides zlib version 1.2.3 which apparently is too > old for what you are doing. For now I am just building from commit > 69867c33 which pre-dates the inclusion of the zlib version checks. Is > there a convenient way to make the gzipped dump and restore optional, so > that I can continue to keep up with other changes? > > If not I can look into building a newer version of zlib for use with > notmuch. Unfortunately I can't think of a simple change to make gzipped dump and restore optional; somewhat ironically we actually need the later zlib for dumping uncompressed backups. This is clearly not a feature we want to take away. I guess it would be possible to write a compat shim on top of zlib that implemented the passthrough that we need. Tomi Ollila, who runs notmuch on various old systems, might a have a comment about that. Meanwhile, unlike libc, it should be possible to compile a newer zlib. d