configure: WARNING: unrecognized options: --with-elispdir, --with-etcdir ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no_multilib-j4-20211209-113836 ------------------------------------------------------------------- The log matches a QA pattern or a pattern requested by a Gentoo developer.
Created attachment 758312 [details] app-emacs:mew-6.8:20211210-185819.log
Created attachment 758313 [details] emerge-history.txt
Created attachment 758314 [details] etc.portage.tar.bz2
I cannot reproduce this. The log shows that both options are known and have the intended effect: > *************************** > Mew configuration results > *************************** > > use emacs : /usr/bin/emacs > elisp files should go : /usr/share/emacs/site-lisp/mew > etc files should go : /usr/share/emacs/etc/mew I suspect that the warning is triggered by your EXTRA_ECONF. Does it still occur without it?
(In reply to Ulrich Müller from comment #4) > I suspect that the warning is triggered by your EXTRA_ECONF. Does it still > occur without it? pretty sure, that it does it occurre w/o it.
(In reply to Toralf Förster from comment #5) > (In reply to Ulrich Müller from comment #4) > > > I suspect that the warning is triggered by your EXTRA_ECONF. Does it still > > occur without it? > > pretty sure, that it does it occurre w/o it. But I do bet that then there's a similar QA warning
I'd much prefer a log to "pretty sure" or "I do bet". :)
here you go ;)
Created attachment 758466 [details] app-emacs:mew-6.8:20211211-100333.log
Created attachment 758467 [details] emerge-history.txt
Created attachment 758468 [details] etc.portage.tar.bz2
(In reply to Toralf Förster from comment #11) > Created attachment 758468 [details] > etc.portage.tar.bz2 This still has EXTRA_ECONF="--enable-option-checking=warn" in make.conf.
I've left a comment in the tracker, see bug 828551 comment #2. Closing.