[Octave-bug-tracker] [bug #58330] Do not warn in ./configure for explicit --without-XXX arguments

[Andrew Janke]

URL:
  <https://savannah.gnu.org/bugs/?58330>

                 Summary: Do not warn in ./configure for explicit
--without-XXX arguments
                 Project: GNU Octave
            Submitted by: apjanke
            Submitted on: Thu 07 May 2020 04:54:07 PM EDT
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: Any

    _______________________________________________________

Details:

Following up on https://savannah.gnu.org/bugs/?58321.

The current build system, in at least some cases, emits warnings like
"WARNING: blah is disabled" when the caller supplies --without-XXX arguments,
such as --without-fltk. (Though FLTK in specific is fixed now.)

If the user is explicitly asking for --without-XXX, we should assume they know
what they're doing, and not warn about the absence of XXX, since that was the
requested behavior. Let's modify the `configure` script to only emit warnings
for unavailable/non-selected components if they were selected by default and
then found to be absent by detection, and never warn about components that
were explicitly disabled using --without-XXX options to configure.




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58330>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/