The emerge log for 18.0_beta4 shows that these configure flags are now unknown (sorted for easier viewing): --disable-crashreporter, --disable-dbus, --disable-gconf, --disable-gnomeui, --disable-gnomevfs, --disable-install-strip, --disable-mailnews, --disable-necko-wifi, --disable-pedantic, --disable-profilelocking, --disable-startup-notification, --disable-strip, --disable-system-sqlite, --disable-system-sqlite, --disable-tests, --disable-updater, --enable-application, --enable-default-toolkit, --enable-extensions, --enable-gio, --enable-gstreamer, --enable-methodjit, --enable-official-branding, --enable-ogg, --enable-optimize, --enable-pango, --enable-system-cairo, --enable-system-ffi, --enable-system-hunspell, --enable-tracejit, --enable-wave, --with-default-mozilla-five-home --with-nspr-prefix, --with-nss-prefix, --with-system-jpeg, --with-system-libevent, --with-system-libvpx, --with-system-nspr, --with-system-nss, --with-system-png, --with-system-zlib,
The log is incorrect, it does not understand how configure works in products like mozilla. *** This bug has been marked as a duplicate of bug 446662 ***
It is configure itself which warns about the unrecognized options.
yes, but the build system calls multiple ./configure's within the work dir, and each one only uses a subset of the options.
Ah. OK. Thanks.