Hiya,
I'm reviewing an octave package[1] that generates an arch specific mex
file. As I understand it, this should go to
/usr/lib64/octave/packages/%{name}-%{version} (%{octpkglibdir}), while
the other noarch files go to
/usr/share/octave/packages/%{name}-%{version} (%{octpkgdir}). This is
the case:
drwxr-xr-x /usr/lib64/octave/packages/mmclab-1.7.9
-rwxr-xr-x /usr/lib64/octave/packages/mmclab-1.7.9/mmc.mex
drwxr-xr-x /usr/share/doc/octave-mmclab
-rw-r--r-- /usr/share/doc/octave-mmclab/AUTHORS.txt
-rw-r--r-- /usr/share/doc/octave-mmclab/README.txt
drwxr-xr-x /usr/share/licenses/octave-mmclab
-rw-r--r-- /usr/share/licenses/octave-mmclab/LICENSE.txt
drwxr-xr-x /usr/share/octave/packages/mmclab-1.7.9
-rw-r--r-- /usr/share/octave/packages/mmclab-1.7.9/besselhprime.m
-rw-r--r-- /usr/share/octave/packages/mmclab-1.7.9/besseljprime.m
-rw-r--r-- /usr/share/octave/packages/mmclab-1.7.9/besselyprime.m
-rw-r--r-- /usr/share/octave/packages/mmclab-1.7.9/cart2sphorigin.m
...
However, @fangq (CC'd) reports that the mex file does not load in
Octave[2]. The path() in octave does not return %{octpkglibdir} either
when I check it. Could someone please point out what we're missing here?
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1760617
[2]
https://bugzilla.redhat.com/show_bug.cgi?id=1760617#c28
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London