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 EE31D4196F2 for ; Wed, 14 Apr 2010 10:37:24 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -2.89 X-Spam-Level: X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, T_MIME_NO_TEXT=0.01] autolearn=ham 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 LMrY2JjjryDA; Wed, 14 Apr 2010 10:37:24 -0700 (PDT) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 2F9F4431FC1; Wed, 14 Apr 2010 10:37:24 -0700 (PDT) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id CF294568DE1; Wed, 14 Apr 2010 10:37:23 -0700 (PDT) From: Carl Worth To: Aaron Ecay , notmuch Subject: Re: Build problems on OS X In-Reply-To: <4bc25ea0.86c3f10a.45a3.ffff80d3@mx.google.com> References: <4bc25ea0.86c3f10a.45a3.ffff80d3@mx.google.com> Date: Wed, 14 Apr 2010 10:37:23 -0700 Message-ID: <87wrwaey0c.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" 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: Wed, 14 Apr 2010 17:37:25 -0000 --=-=-= On Sun, 11 Apr 2010 19:43:27 -0400, Aaron Ecay wrote: > In the process of updating to the latest sources, I've discovered that notmuch > no longer builds on OS X. Hi Aaron, Thanks so much for following up here. This transition to building/installing a shared library (and not using libtool) is the big one as for as build-system portability goes. So I did expect to see a patch series here. I'm optimistic that going forward, we won't have constant breakage. Though I did have a suggestion to call ldconfig implicitly when doing "make install". Is that the same command on OS X or is it different? > As a reply to this email, I'll be sending 4 patches. I'll follow up to some of these individually. > The fourth patch I am not sure of. Even after adding the proper command line > flags to build the shared binary on OS X, I get symbol not found errors for > Glib/Gmime symbols. The shared binary links against the shared lib, which in > turn links against Glib and Gmime, but it appears that at least on OS X the > linker won't follow these second-order links, and the notmuch shared binary > must be linked against Glib/Gmime directly. This patch fixes the build for > me, but it may not be correct on Linux/other Unices. You're correct that it is incorrect on Linux. :-) Debian's program for checking package correctness (lintian) complains if a binary is linked directly against a library when the binary doesn't actually reference any symbols from that library, (but instead references symbols from other libraries that in turn reference the library). So we do want to avoid this excess linking. > I can resubmit this patch to add the extra linker flags only when > building for OS X. If anyone knows how to get the OS X linker to > behave like the Linux one in this regard, that will likely be a better > solution. Reworking that patch would be great. I don't have any suggestion for fixing the linker though. :-P -Carl --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLxf1T6JDdNq8qSWgRArsZAJkBW3DSJajFgxoGqVoHvL3fIq6m+gCdEy/2 7deNd4OWW06bhg0Gx0SQYyI= =x7ns -----END PGP SIGNATURE----- --=-=-=--