Arch Linux User Repository

Hi, I'm tackling the problem with the add-ons installation, where the installer can't write to /usr/local/MATLAB/R2022b. I think we should avoid manual chmods or chowns, as it would be easy to mess up with the permissions, so I created a matlab group with rwx permissions, which owns the tree starting at /usr/local/MATLAB/R2022b. The PKGBUILD sets up the correct permissions, so after installing MATLAB, you should just add yourself to that group, re-login and then you should be able to install add-ons. So far I'm able to start the installer, download the add-on archive, but when I get to Performing post-installation tasks. This may take a few minutes..., an error occurs, and the installer logs End - Unsuccessful Exception: java.lang.InterruptedException without further information.

If anyone wants to help me resolve this issue, here is the repo: https://github.com/Rubo3/matlab-aur/tree/addons.

I updated the PKGBUILD to MATLAB R2022b. Sorry it took so long. Here are the main changes:

• The dependencies have been updated according to namcap (thanks @sukanka), and are now managed via the matlab-meta meta package, now it's really easy to play around with them, as you don't have to rebuild the entire MATLAB package (thanks @bbaserdem). I still don't know the exact dependencies needed by MATLAB, as I don't use all its toolkits and whatnots. As always, please tell me if you find something.
• The MATLAB installer now outputs its logs in install.log, under the same directory of the PKGBUILD, so that you can check whether something went wrong even if it didn't fail (e.g. when you need a new license or installation key because the major version changed).
• I moved python-matlabengine to its own repo, which is built from upstream and works for the latest MATLAB versions. Currently it supports Python 3.9 and 3.10. If you have other needs, you can find the installation instructions here. Since the source files are still provided in your local MATLAB installation under $_instdir/extern/engines/python, building it and packaging it here was really just a convenience. I would like to know how many users of this PKGBUILD really need to spoof their Python version, so that we can reason about putting back that extra logic in the other PKGBUILD.
• I also removed the Mesa workaround and the optional compilers, are they still needed?

READ THE README FILE IN THE REPO. NO AUR HELPERS SUPPORTED. ONLY ARCHLINUX AS OS IS SUPPORTED. YOU SHOULD BE BUILDING THIS PACKAGE USING MAKEPKG, NOTHING ELSE WILL BE SUPPORTED. Please only post issues here AFTER you followed the README.md. located at the root of this repo: https://aur.archlinux.org/cgit/aur.git/tree/README.md?h=matlab Due to a lot of comments; my spam filter is removing AUR notifications which keeps me from responding timely to issues in packaging, please don't post if you don't do some troubleshooting yourself. If your skill level is not up to troubleshooting (or following simple instructions as laid out by the readme), just install matlab locally, without using this package.

• This PKGBUILD is NOT a minimal installation; as it has (hard) dependencies to gcc8 to force MATLAB to use system libraries. While generally not required; this PKGBUILD is trying to make MATLAB work with the system rather than with the mathworks-provided binaries. Currently it also does the python integration so that jupyter can be used with it.
• This will only work with 2020b version; and will not work with earlier (or later) versions.
• This PKGBUILD DOES NOT DOWNLOAD MATLAB FOR YOU. The EULA prevents redistribution of the software. Read the README.md file contained in the PKGBUILD repo. This is essentially a script to integrate an existing matlab installer with your archlinux system; it does NOT come with any software from Mathworks. You most likely cannot build this package using an AUR helper; you NEED to manually provide files; and to get the files you need a valid MATLAB licence. The process of fetching the files is described in detail in the README.md in the repo. (You can use any valid credentials to install the package using this PKGBUILD; including a licence file that does not match the machine; but you will need to reactivate matlab by using activate_matlab.sh with root privileges.)
• Current users; please help me test and trim the dependencies list, and submit your personal fixes for issues if you have them so they can be added to the PKGBUILD. (Cuda related contributions; if needed would be good as I don't have nvidia GPU's to test compatibility.)
• To use jupyter with matlab; you also need jupyter-matlab_kernel(-git).

@flying-sheep that is a real pain. I am not sure what the best strategy is. One option is to just not create the links at all and let people add /opt/tmw/matlab/bin to $PATH. I think mmex is confusing. I am also worried that deploytool, mbuild, and mcc might also end up with eventual name clashes. Maybe going with something like mex-matlab. For now, the workaround is pretty simple. You can delete "mex" from line 76 of the PKGBUILD or change "${pkgdir}/usr/bin/${_executable}" to "${pkgdir}/usr/bin/${_executable}-matlab" on line 77.

much better yeah! my only problem is that /usr/bin/mex exists in texlive-bin – maybe we should rename matlabs “mex”? (into ‘mmex’ or something)

I have rewritten the PKGBUILD such that it now only supports the most recent version of MATLAB. I have also created version specific packages back to r2010b (https://aur.archlinux.org/packages/?O=0&SeB=n&K=matlab&outdated=&SB=n&SO=a&PP=50&do_Search=Go). If you want to install an older version, use one of the version specific packages. This change makes the PKGBUILD must easier to maintain and understand.

@daniel_shub When I run the command you gave it outputs 'false'. And I have Matlab 2015a installed using a modified version of this PKGBUILD: https://gist.github.com/anonymous/af28f52e890444dd643f Not sure how this helps though?

@daniel_shub That's a great idea. I'd suggest using split packages and meta packages for this. For example, we can have the base package in the split package named "matlab" be a meta package for the latest version, and have it be a split package that generates all the matlab-r$versions ones... Shoot me an email and we can figure out if it's easier to do this via github PRs or comaintainership?

I have been unable to get hardware based opengl working since r2014b and the switch to HG2. This has slowed me down from updated the PKGBUILD. I have tried it on different hardware, so I think it is either a missing package or a configuration issue. Can anyone get $ matlab -nodesktop -nosplash -r "opengl info; exit" | grep Software to output false with r2014b or newer?

@ido I am happy to help out again. I never really intended to let it slip as bad as I did. I have never really been happy with the PKGBUILD and it is not the one I use. I think I tried to make it do too much in an attempt to avoid making multiple packages. I propose we simplify the PKGBUILD to only handle the current release and then create packages like matlab-r2015b, matlab-r2015a, ... matlab-r2010b for people who want older versions. This is in fact how I actually manage my installations of MATLAB so it would be simpler for me.

@SibrenVasse I can build an uncompressed package with only a base MATLAB installation in about 10 minutes on my laptop. Adding toolboxes adds time. It takes me a couple of hours to build and compress the package with all the MATLAB toolboxes. The final package can be upwards of 5 GB.

@flying-sheep the PKGBUILD explains that you will need both the software (an iso file) and a file installation key (a fik file) to build the package. To run MATLAB you will also need a license file (a lic file). Some people have reported that the license file is also required to create the package for network licenses. Do you have a copy of the software, a file installation key and the license?

As mentioned in the previous comment, this package should depend on ncurses5-compat-libs.