From: Nate Eagleson <nate@nateeag.com>
To: notmuch@notmuchmail.org
Subject: build failures on Mac OS X 10.6.8 - diagnosis
Date: Tue, 2 Jun 2015 16:40:59 -0400 [thread overview]
Message-ID: <7156CF8E-BE69-48C0-ACB8-88C7E68CD4BB@nateeag.com> (raw)
Hi folks,
I'm trying to move from Apple's Mail.app in favor of offlineimap/notmuch, but
I've run into a build failure on Mac OS X 10.6.8.
The failure was reported on this list a few months ago, but no explanation or
solution was found:
http://notmuchmail.org/pipermail/notmuch/2015/020531.html
By appending `-Wl,-t` to `FINAL_NOTMUCH_LDFLAGS` in Makefile.local, I
got 10.6.8's ld to dump the list of archives and dylibs that are being
linked in the failed compile.
That list includes `/usr/lib/libutil.dylib`, but not notmuch's built-in
`util/libutil.a`.
I have not found a sane way to tell 10.6.8's ld to prefer libutil.a over
libutil.dylib.
My first thought was that there should be an option to prefer archives over
dylibs, but that does not seem to exist in 10.6.8's version of ld.
Instead, people are recommending absolute paths when you need to link an
archive file in preference to existing dylibs:
http://lists.apple.com/archives/darwin-development/2003/Sep/msg00008.html
http://stackoverflow.com/questions/844819/how-to-static-link-on-os-x
As a simple test, I hardcoded an absolute path to libutil in
FINAL_NOTMUCH_LDFLAGS, and the compile succeeded.
So, it seems like getting the path to the Makefile's parent directory and
using it to specify an absolute path to libutil.a would address this issue without
introducing new ones.
Does this sound like a sane solution? Would a patch to do this be accepted?
If not, what would be a better way to solve this?
Thanks.
-Nate
next reply other threads:[~2015-06-02 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 20:40 Nate Eagleson [this message]
2015-06-03 6:00 ` build failures on Mac OS X 10.6.8 - diagnosis Tomi Ollila
2015-06-03 20:15 ` J. Lewis Muir
2015-06-05 19:26 ` Nate Eagleson
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=7156CF8E-BE69-48C0-ACB8-88C7E68CD4BB@nateeag.com \
--to=nate@nateeag.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).