octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #60099] build fails without cholmod


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #60099] build fails without cholmod
Date: Tue, 23 Feb 2021 03:17:58 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36 Edg/88.0.705.74

Update of bug #60099 (project octave):

             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #7:

I agree with Rik. If a developer/tester tries to build from the repository, we
probably can expect them to read the respective instructions (e.g. [1] for
instructions on Ubuntu/Debian).

Also the condition outlined in comment #4 is incomplete. Like Rik already
wrote: If a user builds from a release tarball, these dependencies *are*
optional because the documentation is already included. No need to mandate
"--disable-docs" in that case.

If a configuration fails with a release tarball, this would be a valid bug.
Like it is, I'll close this report with the status it already has ("won't
fix").

@Ernst: Recently you opened a lot of reports where you asked for help with
XYZ. (Often rephrased to something like "Octave doesn't have a function to do
XYZ" or "Octave fails on doing XYZ".)
Many of those are good questions. But we have to close those reports as
"invalid" or "won't fix" on the bug tracker.
Please, use one of the more appropriate channels for those questions (like the
help mailing lists, discourse, or IRC [2]).

[1]: https://wiki.octave.org/Octave_for_Debian_systems#The_right_way
[2]: https://www.gnu.org/software/octave/support

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]