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

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

[Octave-bug-tracker] [bug #64897] OCTAVE_QUIT macro no longer works in C


From: Sébastien Villemot
Subject: [Octave-bug-tracker] [bug #64897] OCTAVE_QUIT macro no longer works in C MEX file
Date: Wed, 15 Nov 2023 11:52:21 -0500 (EST)

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

                 Summary: OCTAVE_QUIT macro no longer works in C MEX file
                   Group: GNU Octave
               Submitter: svillemot
               Submitted: mer. 15 nov. 2023 16:52:18
                Category: Libraries
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: GNU/Linux
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: mer. 15 nov. 2023 16:52:18     By: Sébastien Villemot <svillemot>
Consider the following C MEX file:


#include <mex.h>
#include <octave/quit.h>

void
mexFunction(int nlhs, mxArray *plhs[],
            int nrhs, const mxArray *prhs[])
{
  OCTAVE_QUIT;
}


It is compiled with Octave 9 (hg ID b5e433b52bc3) using the following
command:

mkoctfile -mex helloworld.c


Then the MEX fails to load under Octave 9:

$ octave
GNU Octave, version 9.0.0
[…]
octave:1> helloworld
error: /tmp/helloworld.mex: failed to load
Incompatible version or missing dependency?
/tmp/helloworld.mex: undefined symbol: octave_quit_c
octave:2> 


I don’t know to which extent this is supported, but at least it used to work
for Octave 8.

I guess the octave_quit_c symbol is not exported in liboctave. The changeset
that triggers this issue seems to be 5f0b8101234e.

Thanks,







    _______________________________________________________

Reply to this item at:

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

_______________________________________________
Message posté via Savannah
https://savannah.gnu.org/




reply via email to

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