bug#66068: removing the WebKit when webkit2gtk3-2.42.5-1.el9.x86_64 will not alllow RL9 to configure

[Eli Zaretskii <eliz@gnu.org>]

> From: Doug Maxey <emacs-bugs@maxeygroup.tech>
> Date: Sun, 22 Sep 2024 21:14:06 -0500
> 
> On Sun, 2024-09-22 at 08:05 +0300, Eli Zaretskii wrote:
> > 
> > ...
> >  $ make extraclean
> >  $ git clean -fdx
> >  $ git pull
> >  $ ./autogen.sh
> >  $ ./configure [...]
> > 
> > where [...] are your usual configure options, but without anything
> > related to xwidgets (and please show the exact configure options you
> > use, as your report above doesn't).
> > 
> > The xwidgets option is off by default, so if you reconfigure Emacs
> > correctly, you should have a build without them (since your
> > webkit2gtk
> > version is not one of those which can be safely used with Emacs). 
> > The
> > output of the configure script above seems to indicate that somehow
> > the configure script was invoked with "--with-xwidgets" option,
> > because otherwise the "checking for webkit2gtk-4.1" part was not
> > supposed to have been done.  E.g., on my GNU/Linux system, invoking
> > the configure script without "--with-xwidgets" option goes straight
> > from cairo to freetype2 testing, bypassing the webkit2gtk-4.0 test:
> > 
> >   checking for cairo >= 1.8.0... yes
> >   checking for freetype2... yes
> >   checking for fontconfig >= 2.2.0... yes
> > 
> > So something in your case is still telling the configure script to
> > build with xwidgets.  "make bootstrap" re-runs the configure script
> > with the same options you used last time, so doing that will not
> > necessarily fix the problem.
> 
> Thank you, the instructions above did fix the issue.
> 
> For the record, my current configure options are
> --prefix=/opt/emacs --with-cairo-xcb --with-imagemagick \
> --with-tree-sitter --with-x --with-x-toolkit=gtk3
> 
> The instance above was with no flags for bootstrap, normally I use
> make bootstrap $configure
> which is all the above options.
> 
> But I missed that bootstrap cached them.

Thanks for telling us, but please in the future use Reply All to keep
the bug tracker on the CC list.