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).

Couple tidbits;

I'm able to build with just the following makedepends, though my PKGBUILD is slightly different than this one. But mostly similar; as the PKGBUILD is based on mine; and from people whom I used as templates for the previous PKGBUILD.

gendesk
coreutils
findutils
python
ca-certificates
cairo
fontconfig
glib2
krb5
libgcrypt
libselinux
libxcrypt-compat
make
mesa
pam
unzip
util-linux-libs

Do not know if this is the minimal building set; but it is pretty small. Also; in your pkgbuild, the first array of dependencies is enough for me to run matlab without issues. The second array (which I had in the pkgbuild before) seems unneccessary; or at least feature dependent which I did not try. I personally opt to manage dependencies using a metapackage now, since I don't want to reinstall matlab to try new dependencies.

I see that this pkgbuild changes pkgver depending on the installation media. However; it probably won't work for anything 2020> , location of binaries and libraries and their versions are all different. The fixes in the python engine and the package_matlab() version will fail on most older versions. Since it only is guaranteed to work with 2022a, maybe dynamic pkgver is not a good idea?

I initially wrote the python spoofing based on some stuff I found online and through trial and effort. I switched methods; instead of making matlab think it's a lower number of python that is being run I just edited so that python engine thinks it supports 3.10. Have not been able to test if it works this way; but the previous spoofing is disabled (python 3.10 changed the way how sys.version_info works so you can't set it to a tuple, and the engine functions uses different methods which is non-trivial to spoof all around.) My solution is in my pkgbuild here.

Also; my suggestion on people with intel gpu, is that the default driver for mesa is iris; but matlab does not work with it. I used to use i956, but since december 2021; it's out of mesa due to being ancient. zink driver seems to work; so you can launch matlab with MESA_DRIVER_OVERRIDE=zink and hardware acceleration works.

Any chance that MATLAB is lying to you? They have been known to sweep OpenGL issues under the rug

https://www.mathworks.com/matlabcentral/answers/239279-hardware-based-opengl-on-linux#answer_220778

"In the three cases listed previously hardware accelerated versions of Mesa are in fact being used. The problem is that the value of the OpenGL info 'software' field is actually incorrect. This issue has been fixed in R2016a."

Maybe they broke something again.

Hi, I messed up my MATLAB installation when I wanted to add additional packages from the GUI. I then decided to uninstall it with sudo pacman -R matlab, and then run the installation again. I followed the installation instructions, this time also installing additional packages. The installation seemed to run correctly, but now when I start matlab from the terminal, I get:MATLAB is selecting SOFTWARE OPENGL rendering., and with $ matlab -nosoftwareopengl, I get nothing. What can I do? Where can I look for error messages or hints of what may be wrong? I'm considering trying to install this again in a VirtualBox.

Also, I keep getting:

Error: No classpath definition jar found.
==> ERROR: A failure occurred in build().

Which apparently means one of the addons can't find the jars in ./matlab/java (./src/matlab/java) that it needs. i'm on a new system and my xorg/i3 isn't quite set up completely. i'm not sure if this is something I can fix by setting the java classpath env var or whether it's actually missing files.

here are the extensions i'm installing:

"MATLAB", "Simulink", "Bioinformatics_Toolbox", "Control_System_Toolbox", "Curve_Fitting_Toolbox", "Deep_Learning_Toolbox", "Econometrics_Toolbox", "Financial_Instruments_Toolbox", "Financial_Toolbox", "Instrument_Control_Toolbox", "MATLAB_Coder", "MATLAB_Compiler", "MATLAB_Report_Generator", "Optimization_Toolbox", "Partial_Differential_Equation_Toolbox", "Reinforcement_Learning_Toolbox", "Robotics_System_Toolbox", "Simulink_3D_Animation", "Simulink_Check", "Simulink_Code_Inspector", "Simulink_Coder", "Simulink Control_Design", "Simulink_Test", "Statistics_and_Machine_Learning_Toolbox", "Symbolic_Math_Toolbox", "Wavelet_Toolbox"

after running the matlab installer, the install.sh script runs makepkg, which can't find these files in the prepare() phase

./src/matlab/installer_input.txt ./src/matlab/install.txt

it seems to pick these up if I just copy them to the required location.

however, running the install.sh script a second time replaces the matlab.tar file with a version of MATLABROOT that has its files deleted. it might help to error out if matlab.tar already exists bc it's been a bit confusing.

another issue that i'm running into is that Ctrl-c on big cp ops leaves my /tmp/ directory full, which causes the script to error again.

@TheHardew @AlexBocken fixed now, thanks. Can't say how it worked without issues until few weeks ago haha.

I had the same issue as @TheHardew, his proposed fix in line 207 fixed the installation for me.

@Rubo thank you so much for your work on updating this PKGBUILD!

I think it should be ls -d at line 207 in "Changing around locations if spoofing is needed..."? I got errors without it:
mv: cannot stat 'dependency_links.txt'$'\n''PKG-INFO'$'\n''SOURCES.txt'$'\n''top_level.txt': No such file or directory

@rellieberman the MATLAB installer will not care, but you will likely run into problems with pacman if you either try and reinstall the current version or upgrade the package to a new version.