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

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

[Octave-bug-tracker] [bug #42352] pkg install fails if --disable-docs is


From: Bob McKay
Subject: [Octave-bug-tracker] [bug #42352] pkg install fails if --disable-docs is given at build time
Date: Sat, 26 Jul 2014 18:37:16 +0000
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Firefox/31.0

Follow-up Comment #4, bug #42352 (project octave):

"IOW, --disable-docs doesn't save you any build steps, it just prevents files
that are already built from being installed."

Please forgive me if I am misunderstanding. I'm not really clear whether this
is a source code or a packaging issue. But it seems to be not really about the
presence or absence of the doc files, but the presence or absence of a
compatible texinfo in the installing system. It's causing problems in a number
of downstream systems (just google "texinfo octave"); specifically, it is
currently breaking octave in macports. 

The problem seems to be that if texinfo is absent or an incompatible version,
the install defaults to --disable-docs, (which then fails as Patric
describes). If this is the intended behaviour, it needs to work (i.e. if
--disable-docs is to be an option, then it should succeed in building octave
without docs, and specifically without texinfo calls - and in particular,
__makeinfo__.m shouldn't be called in the build). This looks to be non-trivial
to fix. But if it's not the intended behaviour - if --disable-docs builds are
intended to fail with an error message - then octave has a hard dependency on
texinfo, rather than the soft one that is currently described. 

Because it's breaking a number of downstream builds, perhaps it needs to be
characterised as an installation problem  rather than a feature request, with
severity rather higher than 'wish'.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?42352>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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