unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Ryan Schmidt <notmuch@ryandesign.com>, notmuch@notmuchmail.org
Subject: Re: notmuch 0.19 build fails on OS X 10.6 with gcc 4.2.1 with undefined symbols
Date: Thu, 30 Apr 2015 21:52:04 +0900	[thread overview]
Message-ID: <87bni5g4nf.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <F741763B-2B59-4681-B13A-7BC423FD8DC3@ryandesign.com>

Ryan Schmidt <notmuch@ryandesign.com> writes:

> Hello,
>
> I'm a developer with the MacPorts project and I discovered that notmuch 0.19 does not build on Mac OS X 10.6 with its gcc 4.2.1 compiler. The errors are:
>
> Undefined symbols:
>   "_hex_decode_inplace", referenced from:
>       _parse_tag_line in tag-util.o
>   "_gz_error_string", referenced from:
>       _notmuch_restore_command in notmuch-restore.o
>       _notmuch_restore_command in notmuch-restore.o
>   "_gz_getline", referenced from:
>       _notmuch_restore_command in notmuch-restore.o
>       _notmuch_restore_command in notmuch-restore.o
>   "_hex_encode", referenced from:
>       _notmuch_database_dump in notmuch-dump.o
>   "_talloc_strndup_named_const", referenced from:
>       _notmuch_restore_command in notmuch-restore.o
>       _notmuch_restore_command in notmuch-restore.o

Those are all supposed to be defined in util/libutil.a. At a glance the
command line looks plausible. It's a long shot, but you could make sure
they are there using e.g.

% nm util/libutil.a

Beyond that, I'm hoping some Mac user will have some ideas.

      reply	other threads:[~2015-04-30 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30  5:20 notmuch 0.19 build fails on OS X 10.6 with gcc 4.2.1 with undefined symbols Ryan Schmidt
2015-04-30 12:52 ` David Bremner [this message]

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=87bni5g4nf.fsf@maritornes.cs.unb.ca \
    --to=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    --cc=notmuch@ryandesign.com \
    /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).