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

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

[Octave-bug-tracker] [bug #59081] [MXE Octave] Octave binary cannot be f


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #59081] [MXE Octave] Octave binary cannot be found by of-image
Date: Tue, 8 Sep 2020 11:28:58 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36 Edg/85.0.564.44

Follow-up Comment #13, bug #59081 (project octave):

Looks like of-image needs Octave for these tests:

## Some functions have been moving between Octave core and the Image
## package so make sure we are not shadowing anything on this
## installation.
##
##  im2double - moved into core for core version 4.2
##  ntsc2rgb - moved into the image package for core version 4.4
##  rgb2ntsc - moved into the image package for core version 4.4

M_FILES=""
m4_foreach([FNAME], [im2double, ntsc2rgb, rgb2gray, rgb2ntsc], [
  AC_MSG_CHECKING([Octave core for function FNAME])
  HAS_FUNCTION=`$OCTAVE -qfH --eval "printf ('%i', exist ('FNAME'))"`
  if test "$HAS_FUNCTION" == 0; then
    AC_MSG_RESULT([no])
    M_FILES="${M_FILES} FNAME.m"
  else
    AC_MSG_RESULT([yes])
  fi
])


So exactly what John wrote in comment #11.

Building a minimal Octave should take only a few minutes if using ccache is an
option.
E.g. jwe's no-extras-debian worker took about 3 minutes for the configure and
compile steps: http://buildbot.octave.org:8010/#/builders/7/builds/1786
Additionally, you'd need to call "make install". But I don't think that will
take very long.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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