[Bug 255291] Make GNU_CONFIGURE option checking fatal
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Apr 21 07:16:20 UTC 2021
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255291
Bug ID: 255291
Summary: Make GNU_CONFIGURE option checking fatal
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Ports Framework
Assignee: portmgr at FreeBSD.org
Reporter: tobik at freebsd.org
CC: ports-bugs at FreeBSD.org
Flags: exp-run?
Created attachment 224322
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224322&action=edit
enable_option_checking.diff
I wonder if an exp-run that adds --enable-option-checking=fatal for
autotools builds would be a good idea. The default is to only print
a warning on wrong options but this would make it fatal.
The goal would be to clean up all the wrong or obsolete configure args
that have accumulated over the years. Later it would also prevent bugs
like bug #255280 where an argument has subtly changed and the maintainer
missed it.
Fallout might look like:
===> Configuring for libpurple-2.14.3_1
configure: error: unrecognized options: --with-python, --with-html-dir,
--disable-gtk-doc
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-ports-bugs
mailing list