From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43754@debbugs.gnu.org, syohex@gmail.com
Subject: bug#43754: [PATCH] configure help message of --with-json
Date: Fri, 02 Oct 2020 16:28:38 +0200 [thread overview]
Message-ID: <87ft6wwvl5.fsf@gnus.org> (raw)
In-Reply-To: <834kndgm47.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 02 Oct 2020 09:47:36 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Any reason why we use OPTION_DEFAULT_IFAVAILABLE for json, and not
> OPTION_DEFAULT_ON? How is it different from libpng or liblcms2 or
> libgnutls?
I wonder whether it's because of this:
case $with_gnutls,$HAVE_GNUTLS in
no,* | ifavailable,* | *,yes) ;;
*) MISSING="$MISSING gnutls"
WITH_IFAVAILABLE="$WITH_IFAVAILABLE --with-gnutls=ifavailable";;
esac
case $with_json,$HAVE_JSON in
no,* | ifavailable,* | *,yes) ;;
*) MISSING="$MISSING json"
WITH_IFAVAILABLE="$WITH_IFAVAILABLE --with-json=ifavailable";;
esac
But if I understand autoconf (and I do not), that shouldn't really
"spread" to the OPTION_DEFAULT_ stuff, should it?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-02 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 0:48 bug#43754: [PATCH] configure help message of --with-json Shohei Yoshida
2020-10-02 1:14 ` Lars Ingebrigtsen
2020-10-02 2:54 ` 황병희
2020-10-02 6:47 ` Eli Zaretskii
2020-10-02 14:28 ` Lars Ingebrigtsen [this message]
2020-10-02 15:06 ` Eli Zaretskii
2020-10-03 17:49 ` Lars Ingebrigtsen
2020-10-03 17:59 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ft6wwvl5.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43754@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=syohex@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://git.savannah.gnu.org/cgit/emacs.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).