From: Eli Zaretskii <eliz@gnu.org>
To: "Nelson H. F. Beebe" <beebe@math.utah.edu>
Cc: 25317@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#25317: emacs-25.1.91 build feedback
Date: Sun, 22 Jan 2017 18:27:35 +0200 [thread overview]
Message-ID: <8337gb5abs.fsf@gnu.org> (raw)
In-Reply-To: <CMM.0.96.0.1485047503.beebe@gamma.math.utah.edu>
> Date: Sat, 21 Jan 2017 18:11:43 -0700
> From: "Nelson H. F. Beebe" <beebe@math.utah.edu>
> Cc: 25317@debbugs.gnu.org, beebe@math.utah.edu
>
> One pain in emacs-x.y.z releases is that if any of the graphics
> libraries (gif, jpeg, png, tiff, ...) and associated header files are
> missing, configure aborts.
>
> I would MUCH rather that it just warned that it would not be able to
> supply that rarely-used feature of viewing bitmap graphics files, and
> carry on with the build.
>
> I had to manually restart a substantial fraction of the builds that
> I've done so far (157 automated, 53 manual). On several platforms, it
> seems difficult to get all of the needed graphics libraries installed,
> without running into package dependencies that say "you can have THIS
> package, but not THAT package, because it depends on YET ANOTHER
> package that cannot be installed on your O/S version".
The behavior was originally like you prefer, but it was changed to
what it is now because users complained that a warning amidst the gobs
of output the configure script pours on users is very hard to notice.
I see your point, but your situation is an unusual one, whereby you
build many different configurations via automated scripts. That's not
how most users build Emacs.
Perhaps a special option --with-PACKAGE=silent could be added to cater
to your use case. But it cannot be the default, IMO.
prev parent reply other threads:[~2017-01-22 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 23:47 bug#25317: emacs-25.1.91 build feedback Nelson H. F. Beebe
2017-01-21 16:45 ` npostavs
2017-01-22 1:11 ` Nelson H. F. Beebe
2017-01-22 5:11 ` npostavs
2017-01-22 16:27 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8337gb5abs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25317@debbugs.gnu.org \
--cc=beebe@math.utah.edu \
--cc=npostavs@users.sourceforge.net \
/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.