From: Eli Zaretskii <eliz@gnu.org>
To: John Yates <john@yates-sheets.org>
Cc: emacs-devel@gnu.org
Subject: Re: Interpreting configure script's results
Date: Fri, 31 Dec 2021 22:30:59 +0200 [thread overview]
Message-ID: <83y240frek.fsf@gnu.org> (raw)
In-Reply-To: <CAJnXXohTTg8Wj9oAuPDOH_Rw80+Z=HcH3ob7+f6UUa1EcCFpRw@mail.gmail.com> (message from John Yates on Fri, 31 Dec 2021 15:08:50 -0500)
> From: John Yates <john@yates-sheets.org>
> Date: Fri, 31 Dec 2021 15:08:50 -0500
>
> Suggestion: Could configure's output be made more informative?
> In particular, when some expected capability fails to be included
> for lack of some header could that be called out?
We follow the same format as configure scripts for any other GNU
package.
When you are about to build a new version of Emacs (or any other
package), you are supposed to run "./configure --help" ans study the
various options to determine which ones are for you. In the "--help"
output, the options that are spelled as --without-FOO mean that the
default is to build _with_ FOO, if that's possible (which for external
library means the development package for the library is installed).
Options that are spelled as --with-FOO mean that the default is to
build without them, regardless of whether the relevant software is
installed. So if some option is listed as --without-FOO, and you
didn't use that --without switch, but the configure reports that it
doesn't build with FOO, it means some software component for that is
missing, or maybe the option is not relevant for your platform.
We usually announce new configure options in the "Installation
changes" section of the NEWS file, which is one other place to look
for information about this stuff.
next prev parent reply other threads:[~2021-12-31 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 20:08 Interpreting configure script's results John Yates
2021-12-31 20:30 ` Eli Zaretskii [this message]
2021-12-31 20:37 ` Eli Zaretskii
2022-01-01 0:10 ` Po Lu
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=83y240frek.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.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 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).