Package Details: matlab 9.4.0.813654-1

Git Clone URL: https://aur.archlinux.org/matlab.git (read-only)
Package Base: matlab
Description: A high-level language for numerical computation and visualization
Upstream URL: http://www.mathworks.com
Licenses: custom
Submitter: ido
Maintainer: greyltc (hottea, petronny)
Last Packager: hottea
Votes: 17
Popularity: 1.165215
First Submitted: 2015-08-15 09:33
Last Updated: 2018-07-22 13:25

Latest Comments

1 2 3 4 5 6 ... Next › Last »

petronny commented on 2018-08-15 10:42

1

For non-network installations, installation from a purchased DVD for example, nowhere will provide this matlab.lic file to users.

Current PKGBUILD requires that users have to run touch matlab.lic to generate a meaningless file before running makepkg.

2

Okay, there are 2 solutions,

  1. you could keep them and set gcc6 as a optional dependency.
  2. you could remove them and set gcc6 as a dependency.

Now gcc6 is removed from the official repositories.
It makes the current way, which is the solution 1, is acceptable now. So you can keep them.

3

Yes, you should set mex options by the way suggested by the wiki pages.

daniel_shub commented on 2018-08-14 15:32

@hottea I think it is a bad idea to include the license file(s) in the PKGBUILD and perform automated activation. License files are really complicated. You can have per user license files and per machine license files. A single installation of MATLAB can have multiple license files. For network installation, a license file is/was required, but for non-network installations, you don't/didn't need a license file. When I first wrote the PKGBUILD I used the license file for building a network installation, but did not include it in the package.

Activation is really stupid, as far as I could determine all it does is download the license file and copy it to the required directory 9it probably tell TMW lots of stuff also).

hottea commented on 2018-08-14 12:44

@petronny emm, you could update the PKGBUILD file. 1. I don't quite understand your point, user just need to provide matlab.lic in the same dir with PKGBUILD, and run makepkg.

2, 3. As for mex, should I remove the unused library files, and set mex opt? According to wiki page, matlab doesn't seem to respect the ${MATLAB}/bin/mexopts.sh customization. Instead it uses ${MATLAB}/bin/glnxa64/mexopts/LANG_glnxa64.xml file.

petronny commented on 2018-08-14 03:53

@hottea

1

You didn't answer me directly. Why matlab.lic is added as source for non-network installations? How could these users even get this file to run makepkg?

2
-  ## See $MATLABROOT/sys/os/glnxa64/README.libstdc++
-  msg2 'Removing unused library files'
-  rm ${pkgdir}/opt/tmw/${pkgname}/sys/os/glnxa64/{libstdc++.so.6.0.20,libstdc++.so.6,libgcc_s.so.1,libgfortran.so.3.0.0,libgfortran.so.3,libquadmath.so.0.0.0,libquadmath.so.0}

See $MATLABROOT/sys/os/glnxa64/README.libstdc++ and you will know why they are removed by @greyltc and me.

3

About mex. See @daniel_shub 's comment.
You should set the recommended compilers since you have listed gcc6 as an optional dependency for mex in PKGBUILD.

4

I guess it's not clear enough for @a36233

petronny commented on 2018-08-14 03:42

@daniel_shub

1
-  msg2 'Creating links for executables'
-  install -d -m755 "${pkgdir}/usr/bin/"
-  for _executable in deploytool matlab mbuild mcc mex; do
-    ln -s "/opt/tmw/${pkgname}/bin/${_executable}" "${pkgdir}/usr/bin/${_executable}"
-  done

He removed the binaries.

2

Some of use are packaging and then distributing via a local (or non-local) repository (MATLAB restrictive EULA be damned)

I agree that including PKGEXT in the PKGBUILD is bad style. But it is acceptable for matlab since it cannot be re-distributed.

daniel_shub commented on 2018-08-13 15:07

@petronny I think including PKGEXT in the PKGBUILD is bad style. It should be left to the user to decide and set via makepkg.conf.

Not all of use package and then install. Some of use are packaging and then distributing via a local (or non-local) repository (MATLAB restrictive EULA be damned). In these cases, the carezy long compression time is worth it to reduce the download bandwidth.

Really wish I had a license for a new version. Trying to get some of the older versions to work is a dependency hell. I would much rather figure out the new dependencies and be done with it.

daniel_shub commented on 2018-08-13 15:01

@hottea in version 9.3.0.713579 release 2 symbolic links were created in /usr/bin which caused the conflict. It looks like Darcy Hu made a modification that fixed the issue.

As for the mex compiler issues. I have been told by TMW that higher versions are not supported. That said, I could never find a test case that failed with a higher version. That said, since it is closed source, when I created the PKGBUILD, I went with the required version and I recommend sticking with that approach.

As for the dependencies, it is a real nightmare. I spent a lot of time starting with a clean chroot and only the base group installed and slowly added dependencies until I could get MATLAB to start. Then I tested things like plotting, sound, the doc viewer, opengl, cuda, etc.

My tests before releasing were matlab_cmd="/bin/matlab -nodesktop -nosplash -r" LC_ALL=C $matlab_cmd "version -java, exit" | grep Java LC_ALL=C $matlab_cmd "opengl info; exit" | grep Software LC_ALL=C $matlab_cmd "x=rand(10, 'single'); g=gpuArray(x); Success=isequal(gather(g), x), exit" | sed -ne '/Success =/,$p' LC_ALL=C $matlab_cmd "doc doc; pause; exit" LC_ALL=C $matlab_cmd "xlabel('BIG FONT', 'FontSize', 42); ylabel('small font', 'FontSize', 12); pause; exit" > /dev/null LC_ALL=C $matlab_cmd "bench, pause; exit" > /dev/null LC_ALL=C $matlab_cmd "load handel; sound(y, Fs); pause(length(y)/Fs); exit" > /dev/null

hottea commented on 2018-08-13 11:59

@petronny 1. You still need a license file from you administrator if you use network installation. For non-network installation, we could automate activate after installation. 2. For mex support with libs issue, you could use higher version of compilers, though it's not officially supported. 3. I think it's clear enough, user need to prepare a tarball matlab.tar from the MATLAB iso image. 4. I don't see such problem. MATLAB is installed in /opt/matlab, so it wouldn't conflict with texlive-bin.

As for deps, since MATLAB is not open source, and there is no deps list provided by MathWorks, I'm not quite sure to keep or remove which deps.

petronny commented on 2018-08-03 05:57

@bbaserdem

Also, is there a specific reason for having non pkg.xz extension?

Because it will take a lot of time to compress the package and then you will extract it just after the compression.

bbaserdem commented on 2018-08-03 01:39

ncurses5-compat-libs is necessary only for >=2016a, which I believe can be phased out. That would leave only a single aur dependency. There is a matlab-2015b package seperately in aur.

Also, is there a specific reason for having non pkg.xz extension?

Also getting a ==> WARNING: Package contains reference to $srcdir.

@a36233 your tar has to have a folder matlab in it, not directly the contents of the matlab installation. Either untar into a directory named matlab then tar -cvf matlab.tar matlab the directory. Or remove the ${pkgname} from the lines that refer to the source files.