Package Details: matlab

Git Clone URL: (read-only, click to copy)
Package Base: matlab
Description: A high-level language for numerical computation and visualization
Upstream URL:
Licenses: custom
Submitter: ido
Maintainer: greyltc
Last Packager: greyltc
Votes: 23
Popularity: 0.63
First Submitted: 2015-08-15 09:33
Last Updated: 2020-02-14 00:00

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

yiping_huang commented on 2017-10-21 17:23

==> Entering fakeroot environment...
==> Starting package()...
-> Starting MATLAB installer
-> Installing license
install: cannot stat '/home/_MyName_/.cache/pacaur/matlab/pkg/matlab/opt/tmw/matlab/license_agreement.txt': No such file or directory
==> ERROR: A failure occurred in package().
:: failed to build matlab package(s)

Same as @xcabal, there is no pacaur/matlab/pkg/matlab/opt folder.

daniel_shub commented on 2017-10-18 13:48

@21violins you need to download the software from the Mathworks and put the software in the build directory. the PKGBUILD tells you how to do this.

21violins commented on 2017-10-18 02:58

I'm getting the following error when trying to install R2017b.

==> Making package: matlab (Tue Oct 17 22:13:06 EDT 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
==> ERROR: Unknown download protocol: file

daniel_shub commented on 2017-09-08 14:14

@Turtizzle the Arch packaging guidelines ( say "Packages should never be installed to /usr/local". I think the best thing to do is probably just create a link in /usr/bin called matlab-mex instead of just mex. If that causes problems for users, then they can add /opt/tmw/matlab/bin to their path variable.

Turtizzle commented on 2017-09-08 07:51

I just moved all executables to /usr/local/bin, as I believe that inofficial packages shouldn't mess with /usr/bin for exactly such conflict reasons anyway. This "fixes" the conflict-problem, unless you rely on directly calling "mex" for whatever reason in your tex-workflow. (Usually, you'd use a building script for that anyway, which probably includes the full path.)

streckus commented on 2017-09-07 17:25

@noel: You can change the PKGBUILD link mex to /usr/bin/matlab-mex or similar. From inside MATLAB, you won't get any difference to normal usage of mex but you might have to point build tools to the right file if you build libraries using mex.

noel commented on 2017-09-06 22:23

conflicts with texlive-bin -> /usr/bin/mex

smldis commented on 2017-09-05 15:06

For new users, notice that you have to follow the Wiki for using this pkg. right?

streckus commented on 2017-09-03 16:59

For Matlab 2017a, the optional dependency gcc47 can be updated to gcc49. (The corresponding AUR package also includes gfortran.)

Turtizzle commented on 2017-08-31 09:19

Hi, I have minor problems installing the package with 2017a.
In particular, some of the files referenced in the package() method of the PKGBUILD do not exist.
Some shell output:

The original content of my installer_input.txt:

The content of the installer_input.txt in the src-folder:

I hope you can help me out with this one, looks like a minor issue, but I don't know much about the matlab installation process... thanks. :)

Edit: I finally had some time to look into it myself... solved it quite easily.
I removed the "silent" option of the installer, then it told me that a license file was required. There was no license.dat available in our software repository, but a network.lic ... I renamed the file, enabled "_networkinstall" and yea, awesome.