From: Aaron Ecay <aaronecay@gmail.com>
To: notmuch <notmuch@notmuchmail.org>
Subject: Build problems on OS X
Date: Sun, 11 Apr 2010 19:43:27 -0400 [thread overview]
Message-ID: <4bc25ea0.86c3f10a.45a3.ffff80d3@mx.google.com> (raw)
In the process of updating to the latest sources, I've discovered that notmuch
no longer builds on OS X. As a reply to this email, I'll be sending 4
patches. The first two are bugfixes; the third adds the infrastructure to the
Makefiles to build a shared library on OS X, since the Mach-O conventions are
somewhat different than the Linux ones. Modulo makefile style quibbles, this
patch should be correct.
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. 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.
Aaron
next reply other threads:[~2010-04-11 23:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 23:43 Aaron Ecay [this message]
2010-04-11 23:44 ` [PATCH 1/4] Use C++ compiler to link notmuch binaries Aaron Ecay
2010-04-14 17:39 ` Carl Worth
2010-04-11 23:44 ` [PATCH 2/4] Fix up Makefile for build Aaron Ecay
2010-04-14 17:47 ` Carl Worth
2010-04-11 23:44 ` [PATCH 3/4] Add infrastructure for building shared library on OS X Aaron Ecay
2010-04-14 18:01 ` Carl Worth
2010-04-14 18:47 ` Carl Worth
2010-04-14 23:39 ` Carl Worth
2010-04-11 23:44 ` [PATCH 4/4] Add CONFIGURE_LDFLAGS to the notmuch-shared buld command line Aaron Ecay
2010-04-14 18:04 ` Carl Worth
2010-04-14 17:37 ` Build problems on OS X Carl Worth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4bc25ea0.86c3f10a.45a3.ffff80d3@mx.google.com \
--to=aaronecay@gmail.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).