On Tue, 28 Jun 2011 08:00:53 +0100, Robin Green <[email protected]> wrote:
> On Tue, 28 Jun 2011 08:34:44 +0200, Pieter Praet <[email protected]> wrote:
> > notmuch tag -inbox +draft -- folder:${where_your_drafts_reside}
> 
> My notmuch help does not mention "folder:", and indeed folder:drafts as a
> search term is just treated as the words folder and drafts. Perhaps this
> is implemented in git head.

Yes, sorry about that. We're woefully late on a release that will
include this feature. Our current release manager expects that release
within a couple of days at least, so that's good!

> However, when I try to compile git head on Dragonfly BSD, I get this error:
>
> CXX -O2 notmuch-shared
> notmuch-count.o: In function `notmuch_count_command':
> notmuch-count.c:(.text+0x63): undefined reference to `notmuch_database_open'
> notmuch-count.c:(.text+0x9d): undefined reference to `notmuch_query_create'

Ouch. It looks like your linker isn't finding anything in the notmuch
library at all. I wonder what went wrong there. Some things to try would
be:

        make V=1

to see the complete linker command line to see if something is obviously
wrong there.

And otherwise to try a "git bisect" to see when the compilation stopped
working.

To start a bisect, you'll need to know a point where notmuch actually
compiles successfully on your system—0.5 perhaps? Double-check that
with:

        git checkout 0.5        # Get the code from the 0.5 release
        make                    # See if it compiles
        git checkout master     # Come back to master

If that went fine then you can bisect with:

        git bisect start
        git bisect good 0.5     # Indicate that 0.5 is good
        git bisect bad          # Indicate that the current state is bad

After that you'll iterate by running:

        make

Followed by one of the following:

        git bisect good         # If the compile succeeded
        git bisect bad          # If the compile failed

In the end, git should tell you a "first bad commit". Send that output
to the list and we can start pinning down what went wrong. Then you can
finalize your git-bisect run with:

        git bisect reset

Good luck!

-Carl

Attachment: pgpx5F9SniWCd.pgp
Description: PGP signature

_______________________________________________
notmuch mailing list
[email protected]
http://notmuchmail.org/mailman/listinfo/notmuch

Reply via email to