Package Details: matlab

Git Clone URL: (read-only)
Package Base: matlab
Description: A high-level language for numerical computation and visualization
Upstream URL:
Licenses: custom
Submitter: ido
Maintainer: greyltc (hottea)
Last Packager: hottea
Votes: 18
Popularity: 0.806111
First Submitted: 2015-08-15 09:33
Last Updated: 2018-10-13 11:52

Latest Comments

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

bbaserdem commented on 2018-10-15 21:51

@hottea, thats great info. I am not, I am just creating a local tarball of matlab, so I can distribute it easily on my 4 archlinux installations. But knowing the file structure for the tarball is a godsent.

On further inspection, matlab now (since 2018b at least from what I have noticed) installs the products to /tmp/tmw<random> while using the network installer. I don't think this was the previous behavior (and it is bad practice to put 8GB on a tmpfs) do notice that the file is deleted upon installation/exiting; so pause once the installer reports 'installing' and cp the directory out of tmp.</random>

hottea commented on 2018-10-04 03:16

@bbaserdem Hey, if you're license administrator, you could download the product via installer with download only option, see here for detail. A typical matlab tarball look like this:

├── activate.ini
├── archives/
├── bin/
├── etc/
├── help/
├── install
├── installer_input.txt
├── install_guide.pdf
├── java/
├── license_agreement.txt
├── licenses/
├── patents.txt
├── readme.txt
├── sys/
├── trademarks.txt
├── ui/
└── version.txt

Matlab products locate in archives directory.

bbaserdem commented on 2018-10-01 16:50

I was wondering if anyone had any issues installing R2018b. I'm trying to create the tar file using the installer, but it looks like the toolboxes are installed somewhere i dont know. I used to install to a directory called faux, and cancelled the moment toolboxes finished, then merged the two directories. (Not working this time around, Im getting missisng file warnings on the installer)

I tried looking for guides regarding creating the tar but nada. Can anyone help out? (And maybe we can include instructions in PKGBUILD how to properly create tar from the installer?)

PanSi21 commented on 2018-09-29 16:54

:: Parsing SRCINFO (1/2): ncurses5-compat-libs :: Parsing SRCINFO (2/2): matlab ==> Creazione del pacchetto: ncurses5-compat-libs 6.1-1 (sab 29 set 2018 20:53:51 CEST) ==> Download dei sorgenti in corso... -> È stato trovato ncurses-6.1.tar.gz -> È stato trovato ncurses-6.1.tar.gz.sig ==> Validazione di source file con md5sums... ncurses-6.1.tar.gz ... Verificato ncurses-6.1.tar.gz.sig ... Ignorato ==> Validazione delle firme dei sorgenti con gpg in corso... ncurses-6.1.tar.gz ... Verificato ==> Pulizia in corso... ==> Creazione del pacchetto: matlab (sab 29 set 2018 20:53:51 CEST) ==> Download dei sorgenti in corso... -> Download di matlab.tar in corso... curl: (3) Invalid file://hostname/, expected localhost or or none ==> ERRORE: Impossibile scaricare file://matlab.tar L'operazione sta per essere interrotta... Error downloading sources: matlab

hottea commented on 2018-08-16 12:41

@petronny If gcc6 is not listed as dep, then we should not modify mex opts in ${MATLAB}/bin/glnxa64/mexopts/LANG_glnxa64.xml. And gcc6 in AUR is gcc 6.4, not gcc 6.3 which is officially supported by MathWorks.

hottea commented on 2018-08-16 08:30

@petronny matlab.lic is available in your account center in MathWorks website. If you don't have one, then you could/should not install matlab.

petronny commented on 2018-08-15 10:42


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.


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.


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/ customization. Instead it uses ${MATLAB}/bin/glnxa64/mexopts/LANG_glnxa64.xml file.

petronny commented on 2018-08-14 03:53



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?

-  ## See $MATLABROOT/sys/os/glnxa64/README.libstdc++
-  msg2 'Removing unused library files'
-  rm ${pkgdir}/opt/tmw/${pkgname}/sys/os/glnxa64/{,,,,,,}

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


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.


I guess it's not clear enough for @a36233