[Octave-bug-tracker] [bug #60308] mkoctfile function behaves different than in command style

[Martin K]

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

                 Summary: mkoctfile function behaves different than in command
style
                 Project: GNU Octave
            Submitted by: grisu86
            Submitted on: Tue 30 Mar 2021 10:00:12 AM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 6.2.0
         Discussion Lock: Any
        Operating System: GNU/Linux

    _______________________________________________________

Details:

I am currently setting up a m-file to compile mex/oct files on demand in my
project for this reason I tried the following from the octave prompt:


blas_libs = mkoctfile('--print BLAS_LIBS'); 
lapack_libs = mkoctfile('--print LAPACK_LIBS');


which resulted in an error, since the arguments get passed to gcc and the
source file is missing.  On the other hand if I execute


blas_libs = eval('mkoctfile --print BLAS_LIBS'); 
lapack_libs = eval('mkoctfile --print LAPACK_LIBS');


is works. This seems to be a bit inconsistent and from the documentation I
think it is a bit strange that the "print action"  requires a source file to
work. 

Tested on Octave-6.2.0 / Ubuntu 20.04







    _______________________________________________________

Reply to this item at:

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

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