From: Tomi Valkeinen <tomi.valkeinen@iki.fi>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH 1/2] fix compilation without emacs
Date: Tue, 19 Nov 2013 13:02:50 +0200 [thread overview]
Message-ID: <528B455A.70200@iki.fi> (raw)
In-Reply-To: <m2fvqsn036.fsf@guru.guru-group.fi>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
On 2013-11-19 12:43, Tomi Ollila wrote:
> On Tue, Nov 19 2013, Tomi Valkeinen <tomi.valkeinen@iki.fi> wrote:
>> It might be better to exclude the whole emacs directory from build when
>> compiling without emacs, but that's a bigger change.
>
> Well, that change would probably break my build: I configure --without-emacs
> (to disable emacs build during normal build) but then I build emacs MUA
> separately (to just one notmuch.elc file)...
Hmm, isn't --without-xxx supposed to mean that I don't care about xxx,
don't configure it, build it, or do anything else with it.
If you do want emacs, but don't want to compile it right now, that can
be done by giving 'make' the components you do want to build (instead of
all).
> You could look http://article.gmane.org/gmane.mail.notmuch.general/15837
> ( id:"1377630047-27756-1-git-send-email-tomi.ollila@iki.fi" ) instead.
Yep, that one also works for me.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
prev parent reply other threads:[~2013-11-19 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 5:10 [PATCH 1/2] fix compilation without emacs Tomi Valkeinen
2013-11-19 5:10 ` [PATCH 2/2] lib: fix error handling Tomi Valkeinen
2014-01-13 21:15 ` Tomi Ollila
2014-01-15 13:45 ` David Bremner
2014-01-19 0:09 ` David Bremner
2013-11-19 10:43 ` [PATCH 1/2] fix compilation without emacs Tomi Ollila
2013-11-19 11:02 ` Tomi Valkeinen [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=528B455A.70200@iki.fi \
--to=tomi.valkeinen@iki.fi \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).