From: Tomi Ollila <tomi.ollila@iki.fi>
To: Darren McGuicken <mailing-notmuch@fernseed.info>,
Peter Portante <peter.a.portante@gmail.com>,
notmuch@notmuchmail.org
Subject: Re: Regarding notmuch and Fedora 16
Date: Thu, 12 Jan 2012 14:31:39 +0200 [thread overview]
Message-ID: <yf6sjjlf6fo.fsf@taco2.nixu.fi> (raw)
In-Reply-To: <87vcosmn04.fsf@bookbinder.fernseed.info>
On Tue, 03 Jan 2012 22:36:59 +0000, Darren McGuicken <mailing-notmuch@fernseed.info> wrote:
> On Tue, 03 Jan 2012 17:09:39 -0500, Peter Portante <peter.a.portante@gmail.com> wrote:
> > I am interested in using notmuch from within emacs, but have not been
> > able to get the latest version of notmuch (0.10.2) to compile under
> > Fedora 16.
>
> Looks like we have a growing Fedora community, yay! :-)
>
> And it's nothing you're doing wrong, per my reply to the other thread
> F16 is using the current development version of gmime which has API
> differences with the stable version 2.4. The patch that exists isn't
> part of standard notmuch since it in turn breaks 2.4 compatibility.
>
> What's the right way to handle this? I see 2.6 tarballs on gnome... is
> 2.6 officially out there and stable?
Some conditional compilation by #if(def)ing some *GMIME* macro...
While doing something else I passed by these messages:
http://www.mail-archive.com/notmuch@notmuchmail.org/msg05829.html
http://koji.fedoraproject.org/koji/buildinfo?buildID=269819
These seems to provide valuable information to anyone attempting
to compile notmuch with gmime 2.5+
Tomi
next prev parent reply other threads:[~2012-01-12 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 22:09 Regarding notmuch and Fedora 16 Peter Portante
2012-01-03 22:21 ` Jameson Graef Rollins
2012-01-03 22:36 ` Peter Portante
2012-01-03 22:40 ` Jameson Graef Rollins
2012-01-03 22:36 ` Darren McGuicken
2012-01-12 12:31 ` Tomi Ollila [this message]
2012-02-27 8:42 ` Karel Zak
2012-02-27 9:21 ` Tomi Ollila
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=yf6sjjlf6fo.fsf@taco2.nixu.fi \
--to=tomi.ollila@iki.fi \
--cc=mailing-notmuch@fernseed.info \
--cc=notmuch@notmuchmail.org \
--cc=peter.a.portante@gmail.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).