bug#50897: Octave package installation

bug#50897: Octave package installation

[Zacchaeus Scheffer]

[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]

Hi Guix!

After installing octave, I tried to install the image package in octave in
two ways.  One by running:
> pkg install image-<version#>.tar.gz
where image-<version#>.tar.gz is in my cwd.  I also tried installing with:
> pkg install -forge image
In both cases, I had the same problem.  The first error I was getting was:
>configure: error: in `/tmp/oct-6RV451/image-2.12.0/src':
>configure: error: C++ compiler cannot create executables

This error can be fixed by installing gcc-toolchain.  After doing so,
attempting to install image gives:
>ld: cannot find -loctinterp
>ld: cannot find -loctave
repeatedly (full output below).  These libraries seem like they should be
included in the octave installation, and also like they should be absolute
paths.  I looked for any instance of octinterp in filenames and found these
in the octave install:
./include/octave-6.2.0/octave/liboctinterp-build-info.h
./lib/octave/6.2.0/liboctinterp.la
./lib/octave/6.2.0/liboctinterp.so.8.0.1
./lib/octave/6.2.0/liboctinterp.so
./lib/octave/6.2.0/liboctinterp.so.8
./lib/pkgconfig/octinterp.pc
I tried installing image with these in my cwd, but no dice.  Even if these
are the correct library files, octave is installing this in my user
directory so the cwd won't be the same.

I need this to work for a class, so I'm willing to put in some hours (days)
to make this work, but I'm pretty lost if anyone has ideas on where to go
next.

Thanks,
Zacchae

[-- Attachment #2: Type: text/html, Size: 1728 bytes --]

bug#50897: Octave package installation

[Guillaume Le Vaillant]

[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]

Zacchaeus Scheffer <zaccysc@gmail.com> skribis:

> Hi Guix!
>
> After installing octave, I tried to install the image package in octave in
> two ways.  One by running:
>> pkg install image-<version#>.tar.gz
> where image-<version#>.tar.gz is in my cwd.  I also tried installing with:
>> pkg install -forge image
> In both cases, I had the same problem.  The first error I was getting was:
>>configure: error: in `/tmp/oct-6RV451/image-2.12.0/src':
>>configure: error: C++ compiler cannot create executables
>
> This error can be fixed by installing gcc-toolchain.  After doing so,
> attempting to install image gives:
>>ld: cannot find -loctinterp
>>ld: cannot find -loctave
> repeatedly (full output below).  These libraries seem like they should be
> included in the octave installation, and also like they should be absolute
> paths.  I looked for any instance of octinterp in filenames and found these
> in the octave install:
> ./include/octave-6.2.0/octave/liboctinterp-build-info.h
> ./lib/octave/6.2.0/liboctinterp.la
> ./lib/octave/6.2.0/liboctinterp.so.8.0.1
> ./lib/octave/6.2.0/liboctinterp.so
> ./lib/octave/6.2.0/liboctinterp.so.8
> ./lib/pkgconfig/octinterp.pc
> I tried installing image with these in my cwd, but no dice.  Even if these
> are the correct library files, octave is installing this in my user
> directory so the cwd won't be the same.
>
> I need this to work for a class, so I'm willing to put in some hours (days)
> to make this work, but I'm pretty lost if anyone has ideas on where to go
> next.
>
> Thanks,
> Zacchae

Hi,

I was able to build an octave package after specifying the location of
the required libraries using the LDFLAGS environment variable:

--8<---------------cut here---------------start------------->8---
export LDFLAGS=-L${GUIX_PROFILE}/lib/octave/6.2.0
octave
pkg install xyz.tar.gz
pkg load xyz
--8<---------------cut here---------------end--------------->8---

However, it would be better to have an octave-build-system making Guix
able to build, install and setup Octave packages (e.g. Octave Forge
packages).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

bug#50897: Octave package installation

[Zacchaeus Scheffer]

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]

That certainly works as a hack.  I ended up installing from source locally
because I needed it to work now.  It is strange that my local build didn't
encounter this problem when all I did was grab the tarball, untar, cd in and
>./configure --prefix=~/.local && make && make install
which should be more or less equivalent to how guix builds it (build system
is gnu-build-system).  An octave-build-system is definitely a good idea,
but the ability to install octave packages the "normal" way should probably
be resolved first and preserved (just like you can still install emacs
packages through (M)ELPA or through guix).

-zacchae

[-- Attachment #2: Type: text/html, Size: 768 bytes --]