From: Paul Eggert <eggert@cs.ucla.edu>
To: Angelo Graziosi <angelo.graziosi@alice.it>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Failure building Emacs master
Date: Tue, 21 Mar 2017 13:59:08 -0700 [thread overview]
Message-ID: <dd39d481-660f-b16a-16a9-222e07a5285e@cs.ucla.edu> (raw)
In-Reply-To: <a318a810-d9b1-3a29-3d9a-aa44b9dc9fa5@alice.it>
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
>> I specifically asked not to make this the default.
>>
In <http://bugs.gnu.org/26102#39> you asked not to remove the POP source
code. Sorry, I must have missed where you specifically asked not to make
--without-pop the default (which is a different issue).
> ..then you should fix also the configure warning... [*]
I installed the attached patch to try to improve the 'configure'
diagnostics. Please feel free to revert or improve it if you think the
patch makes this confusing area even more confusing.
[-- Attachment #2: 0001-Improve-configure-with-pop-etc.-diagnostics.patch --]
[-- Type: application/x-patch, Size: 2618 bytes --]
next prev parent reply other threads:[~2017-03-21 20:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 16:45 Failure building Emacs master Angelo Graziosi
2017-03-21 18:24 ` Paul Eggert
2017-03-21 19:06 ` Eli Zaretskii
2017-03-21 20:13 ` Angelo Graziosi
2017-03-21 20:59 ` Paul Eggert [this message]
2017-03-22 16:10 ` Eli Zaretskii
2017-03-22 17:48 ` Paul Eggert
2017-03-22 19:52 ` Eli Zaretskii
2017-03-22 18:59 ` Angelo Graziosi
2017-03-22 19:05 ` Paul Eggert
2017-03-22 20:22 ` Eli Zaretskii
2017-03-26 9:37 ` Angelo Graziosi
2017-03-26 14:20 ` Eli Zaretskii
2017-03-22 16:08 ` Eli Zaretskii
2017-03-22 19:57 ` Colin Baxter
2017-03-22 20:12 ` Eli Zaretskii
2017-03-22 20:27 ` Colin Baxter
-- strict thread matches above, loose matches on Subject: below --
2017-03-18 16:53 Angelo Graziosi
2017-03-17 23:03 Angelo Graziosi
2017-03-17 23:07 ` Angelo Graziosi
2017-03-18 5:05 ` Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd39d481-660f-b16a-16a9-222e07a5285e@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=angelo.graziosi@alice.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.