[Octave-bug-tracker] [bug #44753] [OF] control-2.8.0 won't install on Octave built for 64-b Windows

[Philip Nienhuis]

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

                 Summary: [OF] control-2.8.0 won't install on Octave built for
64-b Windows
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Mon 06 Apr 2015 10:10:02 PM CEST
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: other
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

With Octave dev version built with --enable-windows-64 (NOT 64-bit indexing,
but below results are the same for 64-bit IDX)


:
ar -rc slicotlibrary.a ./sltmp/*.o
/usr/bin/ar: /usr/bin/ar: cannot execute binary file
make: *** [slicotlibrary.a] Error 126
make: Leaving directory `/tmp/oct-6fJhlA/control/src'

pkg: error running `make' for the control package.
error: called from 'configure_make' in file
C:\Programs\Octave\Octave32-4.0.0-rc1\share\octave\4.0.0-rc1\m\pkg\private\configure_make.m
near line 96, column 9
>>


If I enter the full Windows path (w. forward slashes) to
<OCTAVE_HOME>/bin/ar.exe in the Makefile rather than the MKOCTFILE macro,
control-2.8.0 installs OK.
I also saw this with the ltfat package, where both /usr/bin/ar and
/usr/bin/ranlib are tried rather than ar.exe and ranlib.exe.

control-2.8.0 installs fine on 4.0.0-rc2 (32-bit).

Apparently mkoctfile gets confused on 64-bit Octave.
Makes me wonder whether mkoctfile gets built in a wrong way for Windows 64-bit
systems (--enable-windows-64 in mxe), and if that might even be related to bug
#44642 (speculation).





    _______________________________________________________

Reply to this item at:

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

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