[Octave-bug-tracker] [bug #40180] pkg.m: search for mkoctfile etc. ignores .exe extension on windows

[Philip Nienhuis]

URL:
  <http://savannah.gnu.org/bugs/?40180>

                 Summary: pkg.m: search for mkoctfile etc. ignores .exe
extension on windows
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Fri 04 Oct 2013 10:44:07 PM CEST
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

(Not sure whether this is "configuration and build system" or "Octave
function")

changeset 17516:21656a949661 (containing patches for missing Octave
components) introduced a number of adaptations for finding executables like
mkoctfile, octave_config_info etc.

Now, in a typical section in ./scripts/.../pkg/private/configure_make:

:
    octave_bindir = octave_config_info ("bindir");
    ver = version ();
    mkoctfile_program = fullfile (octave_bindir, sprintf ("mkoctfile-%s",
ver));
    octave_config_program = fullfile (octave_bindir, sprintf
("octave-config-%s", ver));
    octave_binary = fullfile (octave_bindir, sprintf ("octave-%s", ver));
:
<snip>
:
    if (! exist (mkoctfile_program, "file"))
      __gripe_missing_component__ ("pkg", "mkoctfile");

...the if (! exist.....) clause is false because on Windows mkoctfile, octave
and octave_config_info executables have .exe file name extensions. This isn't
honoured in the stanzas higher up where the full paths to these files are
constructed.

This also happens in mkoctfile.m and many other files.
I have no idea how and where to easily handle this. Use the "ispc" function
and if true, pad ".exe" after the fullfile statements? Would that work on MXE
cross-builds?

Anyway this changeset effectively blocks building binary octave-forge
packages, and invoking mkoctfile.





    _______________________________________________________

Reply to this item at:

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

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