Package Details: octave-general 2.0.0-2

Git Clone URL: https://aur.archlinux.org/octave-general.git (read-only)
Package Base: octave-general
Description: General tools for Octave.
Upstream URL: http://octave.sourceforge.net/general/
Licenses: custom
Groups: octave-forge
Submitter: drizzd
Maintainer: drizzd (wangjiezhe)
Last Packager: wangjiezhe
Votes: 51
Popularity: 0.065931
First Submitted: 2012-03-12 21:56
Last Updated: 2015-11-23 11:53

Latest Comments

drizzd commented on 2015-06-10 08:44

Upgrading fails with conflicts

How to fix: Uninstall the package and packages which depend on it with pacman -Rc <package>, then re-install the new version and packages which depend on it.

See also https://bbs.archlinux.org/viewtopic.php?id=196909.

zsrkmyn commented on 2014-11-04 11:18

Thank you for your reply! I tested the .install script in my machine and several other environments, including building and installing in a clean chroot enviroment using 'devtools'. I am glad that the fault is not caused by the script, and I am really sorry to wrongly report the bug.

I find it that when install `octave' and `octave-general` separately (just using this `` pacman -S octave ; pacman -S octave-general``), it works fine. But when install them together (using `` pacman -S octave octave-general ``), it can be wrong as I metioned before. Adding '_' to the variable or not makes no difference.

zsrkmyn commented on 2014-11-04 10:45

Thank you for your reply! I tested the .install script in my machine and several other environments, including building and installing in a clean chroot enviroment using 'devtools', and I also add `` echo $prefix ; echo $stdlib `` in the .install script. I don't why, '$prefix' and '$libdir' are both null, so "libmpi.so.1" would not be found when executing the script. :-)

drizzd commented on 2014-11-03 20:21

Thank you for noticing this bug. This will be fixed in future updates of the packages. However, I do not see how this has any effect, since the configured $prefix $libdir is the default anyways.

zsrkmyn commented on 2014-11-03 13:27

the command in .install script should be:

`` octave -q -f --eval "pkg prefix $_prefix $_libdir; pkg install -verbose -global /usr/share/octave/$_pack.tar.gz" ``

but not:

`` octave -q -f --eval "pkg prefix $prefix $libdir; pkg install -verbose -global /usr/share/octave/$_pack.tar.gz" ``

otherwise, it can be wrong during the installaltion:

/usr/bin/octave-cli-3.8.2: error while loading shared libraries: libmpi.so.1: cannot open shared object file: No such file or directory
/usr/bin/octave-cli-3.8.2: error while loading shared libraries: libmpi.so.1: cannot open shared object file: No such file or directory
error: command failed to execute correctly

Almost all the "octave-*" packages have this problem.

drizzd commented on 2014-02-06 19:38

I have reported your issue upstream: https://savannah.gnu.org/bugs/index.php?41487

But if you upgrade your octave package -- it's version 3.8.0-2 now -- that probably solves your issue.

noplomplom commented on 2014-02-06 06:08

Build error: http://pastebin.com/4CeL9T8z