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: Kai Torben Ohlhus
Subject: [Octave-bug-tracker] [bug #59081] [MXE Octave] Octave binary cannot be found by of-image
Date: Tue, 8 Sep 2020 06:25:48 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36

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

                 Summary: [MXE Octave] Octave binary cannot be found by
of-image
                 Project: GNU Octave
            Submitted by: siko1056
            Submitted on: Tue 08 Sep 2020 12:25:46 PM CEST
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Installation Failure
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 6.0.90
         Discussion Lock: Any
        Operating System: GNU/Linux

    _______________________________________________________

Details:

When building Octave packages, the distribution built Octave binary seems not
to be exposed to the package configure script.

I suspect, that most mxe build systems have some Octave installed, that is
detected by of-image.  Can someone check his mxe "log" directory for
"of-image" and confirm the detected value for "OCTAVE=''"?



In general I do not like to install an Octave on my system, as I run the
mxe-builds inside Docker containers, that shall be as "clean" as possible.

When looking at the logs, is there a way to set an OCTAVE variable in the same
way it is set for MKOCTFILE and copy the octave binary, for example?

Excerpt from "2020-09-08_of-image_log.txt":


LDFLAGS='-L/buildbot/octave-mxe-stable-w64/build/usr/x86_64-w64-mingw32/lib'
LIBOBJS=''
LIBS=''
LTLIBOBJS=''
MKOCTFILE='/buildbot/octave-mxe-stable-w64/build/usr/bin/x86_64-w64-mingw32-mkoctfile
--verbose'
M_FILES=''
OBJEXT=''
OCTAVE=''


Code where binaries are installed in mxe-octave:

https://hg.octave.org/mxe-octave/file/tip/src/stable-octave.mk#l205


ls -al /buildbot/octave-mxe-stable-w64/build/usr/bin/*oct*
-rwxr-xr-x. 1 root root 949344 Sep  8 17:04
octave-mxe-stable-w64/build/usr/bin/x86_64-w64-mingw32-mkoctfile
-rwxr-xr-x. 1 root root 305168 Sep  8 17:04
octave-mxe-stable-w64/build/usr/bin/x86_64-w64-mingw32-octave-config




Excerpt from "2020-09-08_of-image_log.txt"


[build]    of-image

Failed to build package of-image!
------------------------------------------------------------
image-2.12.0/COPYING
checking for a sed that does not truncate output...
/buildbot/octave-mxe-stable-w64/build/usr/bin/sed
checking for octave... no
configure: error: *** 'octave' not found.
operation= install
mkoctfile=
/buildbot/octave-mxe-stable-w64/build/usr/bin/x86_64-w64-mingw32-mkoctfile
--verbose
arch= x86_64-w64-mingw32-api-v55
prefix= /buildbot/octave-mxe-stable-w64/build/usr/x86_64-w64-mingw32
files= ['image-2.12.0.tar.gz']
verbose= True
Installing
/buildbot/octave-mxe-stable-w64/build/tmp-of-image/image-2.12.0.tar.gz
running ./configure --host='x86_64-w64-mingw32' --build='x86_64-pc-linux-gnu'
cleaning up





    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Tue 08 Sep 2020 12:25:46 PM CEST  Name: 2020-09-08_of-image_log.txt 
Size: 4KiB   By: siko1056

<http://savannah.gnu.org/bugs/download.php?file_id=49764>
-------------------------------------------------------
Date: Tue 08 Sep 2020 12:25:46 PM CEST  Name: 2020-09-08_of-image_log.txt 
Size: 4KiB   By: siko1056

<http://savannah.gnu.org/bugs/download.php?file_id=49765>
-------------------------------------------------------
Date: Tue 08 Sep 2020 12:25:46 PM CEST  Name:
2020-09-08_mxe_build_of-image_log.txt  Size: 11KiB   By: siko1056

<http://savannah.gnu.org/bugs/download.php?file_id=49766>

    _______________________________________________________

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]