unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: Thomas Klausner <tk@giga.or.at>, David Bremner <david@tethera.net>
Cc: Notmuch list <notmuch@notmuchmail.org>
Subject: Re: notmuch-0.18 issues [was Re: notmuch-0.16: realpath() compatibility	issue; clang visibility problem]
Date: Thu, 26 Jun 2014 16:16:31 +0300	[thread overview]
Message-ID: <m2a98z95g0.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <20140626130826.GL11862@danbala.tuwien.ac.at>

On Thu, Jun 26 2014, Thomas Klausner <tk@giga.or.at> wrote:

>
> I had some other issues with 0.18 though.
>
> 1. pkgsrc's copy of rst2man is called "rst2man.py". The configure test
> for this fails, of course, and there is another place where rst2man is
> called directly. I've changed that to rst2man.py locally, but it'd be
> good if configure could test for both names, set a variable to the one
> found, and use the variable in the other place.

There are patches to be reviewed for this.

>
> 2. doc/Makefile.local has "python" hardcoded. pkgsrc supports multiple
> python versions at the same time, with the disadvantage that there is
> no "python" executable, only "python2.6", "python2.7", "python3.3"
> etc. I've passed in the proper executable name as PYTHONBIN and used
> it in the Makefile.

For this we could figure out something...

>
> 3. installation of notmuch-version.el fails, because the install rule
> has no dependency on the generated file notmuch-version.el. I've added
> such a dependency.

This has been fixed in 0.18.1.

>
> The patches I used to make notmuch build are attached, but I can of
> course test other patches if you prefer different solutions. I haven't
> really run this version of notmuch yet.
>
> Cheers,
>  Thomas
> $NetBSD$
>

Tomi

  reply	other threads:[~2014-06-26 13:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 21:47 notmuch-0.16: realpath() compatibility issue; clang visibility problem Thomas Klausner
2014-01-04 12:35 ` Jani Nikula
2014-01-04 12:46   ` Jani Nikula
2014-01-04 12:53     ` Thomas Klausner
2014-01-04 13:06       ` Tomi Ollila
2014-01-04 13:28         ` Thomas Klausner
2014-01-04 12:52   ` Thomas Klausner
2014-01-04 13:18 ` David Bremner
2014-01-04 22:37   ` Thomas Klausner
2014-01-04 22:53     ` Jani Nikula
2014-04-08 11:26 ` David Bremner
     [not found]   ` <20140408123312.GZ5053@danbala.tuwien.ac.at>
2014-06-26 12:02     ` David Bremner
2014-06-26 12:52       ` David Bremner
2014-06-26 13:08       ` notmuch-0.18 issues [was Re: notmuch-0.16: realpath() compatibility issue; clang visibility problem] Thomas Klausner
2014-06-26 13:16         ` Tomi Ollila [this message]
2014-06-26 15:00         ` David Bremner
2017-03-12 16:21         ` David Bremner
2017-03-12 17:24           ` Tomi Ollila
2017-03-12 20:52             ` Thomas Klausner
2017-03-12 16:00 ` notmuch-0.16: realpath() compatibility issue; clang visibility problem David Bremner

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=m2a98z95g0.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    --cc=tk@giga.or.at \
    /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).