[Octave-bug-tracker] [bug #55371] Add configure flag to specify makeinfo path

[Mike Miller]

Follow-up Comment #5, bug #55371 (project octave):

I personally would rather not add a configuration option just to fill in the
default value for makeinfo_program, that's exactly why it's a configuration
variable, so the distribution or the user can set their own preferred default
value.

And I believe adding automatic configuration detection of the full path to
executables at build time to be encoded into the program to use at run time is
in bad form. For example, I recently removed the SED variable from
liboctinterp, because Octave had been encoding the full path to the sed
program for years.

Let's say I build Octave with MAKEINFO set to
/usr/local/texinfo-6.5/bin/makeinfo and that does get stored as the default
value of makeinfo_program that Octave uses at run time. Now what happens when
I distribute that executable to someone else and they don't have
/usr/local/texinfo-6.5 on their system? I think this is not the right
direction to address this.

    _______________________________________________________

Reply to this item at:

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

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