From ArchWiki
Latest comment: 4 March by Eternal Andrew in topic Systemd-nspawn: Wayland / XWayland explanation

Install Supported Compilers

Matlab seems to no longer respect the file and instead use mex_C++_glnxa64.xml mex_C_glnxa64.xml files for compiler configuration. So, I think the section needs update.

R shi (talk) 15:31, 4 February 2018 (UTC)Reply[reply]

Compatibility with Java 7

Whereas this page claims that versions of MATLAB earlier than R2013a are not compatible with Java 7, I have installed and am running R2012a (the last version available for 32-bit Linux) on current 32-bit Arch Linux while having only jre7-openjdk installed without problem. It might be the case that this section needs a qualifier "on 64-bit" I presume or perhaps one that points out (in-)compatibility between MATLAB programs and to MATLAB external Java 7 software on the system, but it's not generally true that one needs to install anything else simply to run MATLAB R2012a.

In fact, except for R2013a and earlier on Mac OS X, MATLAB uses the JVM that it itself provides and which it installs in $MATLAB/sys/java/jre. For R2012a on 32-bit Linux, this is:

>> version -java

ans =

Java 1.6.0_17-b04 with Sun Microsystems Inc. Java HotSpot(TM) Client VM mixed mode

and I have yet to uncover any issue with this. Both while installing and running MATLAB I suppose one might need to be careful to not have any environment variables set that would tell the installer and/or MATLAB to not in fact use its own JVM (such as, from the above link, MATLAB_JAVA) but that's about it.

(I have moreover not encountered the need to install the here mentioned font packages xorg-fonts-100dpi, xorg-fonts-75dpi and xorg-fonts-type1; text within figures displays fine for me without them).

Rene (talk) 01:34, 4 May 2014 (UTC)Reply[reply]

I use 64-bit MATLAB and have no idea what the issues with Java are. I can either use or not use the supplied java or my systems java-7-openjdk with all releases of 64-bit MATLAB between R2010b and R2014a.
I cannot resize the fonts in a figure, xlabel('BIG FONT', 'FontSize', 42); ylabel('small font', 'FontSize', 12); gives the same size font, in all 64-bit releases without xorg-fonts-100dpi installed on the X11 server. My system is running at 96 DPI according to xdpyinfo|grep resolution, so potentially/presumably xorg-fonts-75dpi might be needed on other systems
Dshub (talk) 13:06, 29 May 2014 (UTC)Reply[reply]
Given that we now have confirmation from both 32 and 64-bit (*) the best thing might be to simply do away with that Java warning; I also have no idea what it's about. When googling, I did find people running into install time errors which they orginally blamed on a Java version mismatch, but which turned out to be no more than having a tmpfs on /tmp of insufficient size to host MATLAB's native JVM, which the installer copies to /tmp and runs from there -- at least for version R2012a.
As to the font issue; you're right: also no scaling with your example command for me... but in my case even without having any fixed fonts installed (system-wide). I know little about X11 font-issues other than not WANTING the old core fonts installed, and willl not try to comment on that issue further. Can't say I plot a lot anyway :-/
Would've been sort of good though if the original author of that section had been a bit more verbose about what exact problems he or she encountered...
(*) Well, I haven't tried running MATLAB with the system-native java-7-openjdk; if you want me to test, I can do so tommorow or day after.
Rene (talk) 13:33, 29 May 2014 (UTC)Reply[reply]
I am heavily updating the wiki now. I also created a matlabAUR PKGBUILD on the AUR that hopefully will take care of some of the issues. As for the xorg stuff. I think I originated the solution a couple of years ago (i.e., I found the packages that I needed) at MATLAB answers, but never really tried to document it.
Dshub (talk) 16:51, 29 May 2014 (UTC)Reply[reply]
Looks good to me. Unfortunately, it seems I cannot attach a file either here or on the AUR but I'm locally also using a PKGBUILD, and one that's rather less impressed with the mex/gcc version issue. Specifically, I simply remove the "validate_gcc" calls from (/opt/MATLAB/bin/) "mex" (line 1653) and "mbuild" (line 2372); works fine for MATLAB R2012a and gcc 4.9.0 at least.
A slight heads-up: I saw you install the .xpm icon for older versions of MATLAB and back when I was using Xfce, I had to convert that icon to a PNG since XPM icon rendering in the Xfce menu caused trouble: specifically, it wouldn't scale. In my current PKGBUILD, I do:
convert $srcdir/Matlab_Logo.png -resize ${RES}x${RES}\! $pkgdir/usr/share/icons/hicolor/${RES}x${RES}/apps/MATLAB.png
in which Matlab_Logo.png is [1]. My PKGBUILD depends on hicolor-icon-theme and gtk-update-icon-cache and I run
gtk-update-icon-cache -f -q -t /usr/share/icons/hicolor
from an install= install script; post_install, post_upgrade and post_remove hooks as usual. For RES I use 16, 22, 24, 32, 36, 48 and 64 given that I had those hicolor dirs already anyway, but just one is necessary (also with Xfce).
Rene (talk) 01:48, 30 May 2014 (UTC)Reply[reply]

Using Java-8 with Matlab 2017a

I was getting an exception when starting this version with Java-7. But this did not prevent Matlab from functioning correctly. I tried the newer JVM to verify the error and it is solved.

J605 (talk) 09:44, 22 April 2017 (UTC)Reply[reply]

Installation - steps required for fully working current version

Installation instructions should cover all the steps necessary for a fully working current version on an up-to-date system.

In my case, for 2017b:

  • No AUR package was available - only available method was using the official installer (no biggie)
  • Had to do the libstdc++ fix (which is described twice on the page with slightly different solutions)
  • Had to do the libfreetype fix (which is only mentioned sidenote-style)
  • Had to do the MATLABWindow/pango fix (libgio, libglib, libgmodule, libgobject, libgthread, described as "Addon manager not working" but for me it appeared when launching Simulink)

Luckily it appears so that the Intel Graphics / DRI3 bug has been fixed (I've encountered it last time I've checked, with 2016b). I think providing a list of required fixes as links to respective sections would simply be a nice touch.

Additionally, the instructions could more explicitly cover required packages and the provided full contents of a desktop entry file (if it's not too big).

I can try issuing some of those changes, though first I'd like to hear some opinions. If any other fixes/workarounds that I didn't apply are very often required, please let me know (both for inclusion here and so that I can apply them on my installation).

Akkenoth (talk) 14:46, 14 March 2018 (UTC)Reply[reply]

AUR guide broken

The AUR install guide appears to be broken - the PKGBUILD wants "matlab.tar", as opposed to "". Not sure on how to correct. Ls256 (talk) 13:45, 31 May 2019 (UTC)Reply[reply]

Turned out the archive is still there, but the parent directory is named differently. I think I've edited the section appropriately and it should be up to date now Anana5 (talk) 18:23, 25 November 2021 (UTC)Reply[reply]
There's a couple of other inaccuracies now: It says the installer gives you the option of installing now or only downloading selected modules, but there is no such option. The `rsync` step says to copy `/selected/download/folder/YYYY_MM_DD_HH_MM_SS`, but there is no such folder per default, and it's difficult to tell whether it's supposed to be `/selected/download/folder/MATLAB/R2022b` or some subdirectory of it. I've previously been able to install, currently failing to update. But I remember this as being confusing last time as well Gustaphe (talk) 15:38, 15 November 2022 (UTC)Reply[reply]

Turning on hardware based OpenGL acceleration

In MATLAB 2019a one can run opengl('save', 'hardware') command and restart MATLAB to turn on hardware acceleration. "This command sets your preferences so that future sessions of MATLAB on this computer use the preferred version of OpenGL", as said at (talk) 18:34, 7 January 2020 (UTC)Reply[reply]

terminate called after throwing an instance of 'std::runtime_error' what(): Unable to launch the MATLABWindow application Aborted (core dumped)

Fixed by installing the libselinux package Someonewithpc (talk) 10:49, 21 May 2020 (UTC)Reply[reply]

Systemd-nspawn: Wayland / XWayland explanation

As Wayland grows to be more used I belive there should be a mention of what Wayland users should do differently. This would extend the discussion here: Talk:Systemd-nspawn#Wayland desktop environment inside nspawn. I do not have the expertise to do this, but I believe it would be a worthwhile addition. Eternal Andrew (talk) 16:45, 4 March 2024 (UTC)Reply[reply]