"Nelson H. F. Beebe" writes: > Unfortunately, a further 77 automated builds were broken by this > obnoxious failure: > >>> ... >>> configure: error: The following required libraries were not found: >>> gnutls >>> Maybe some development libraries/packages are missing? >>> If you don't want to link with them give >>> --with-gnutls=no >>> as options to configure >>> ... > > My suspicion is that the gnutls package is needed only for editing > files across a network, which few users ever do. Thus, my strong view > is that, while it is fine for configure to test for the availability > of gnutls, it should NOT be a show-stopper that requires a manual > override and a fresh build attempt with that extra option. It's also used for downloading packages from repositories. It is optional there, but in recent times not using https for this is considered unacceptable (e.g. [1]). You might call this mass hysteria, or you might call it sanity being restored, but either way, I don't think it's accurate that few users will want gnutls. [1]: https://glyph.twistedmatrix.com/2015/11/editor-malware.html > I've expressed the view before on this list that the same should apply > for the various options for libraries that allow emacs to view > bitmap-graphics files, again a feature that few people are ever likely > to use. Yes, in Bug#25317 [2]. I was going to to add an option to make that possible, but I didn't get around to finishing it at the time. [2]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25317#13 > I strongly recommend that configure.ac be revised so that all > --with-XXX=[no|yes] options allow configuration and building to > proceed, regardless of their settings. It is just too painful to have > to spend several unnecessary hours restarting builds to work around > the current undesirable behavior. Here's a patch now, which should give the behaviour you want when passing --with-all=maybe to ./configure. Unfortunately, it's probably too late to get this in for Emacs 26, but hopefully we can smooth things out for version 27.