Trying to install Matlab 7 R14 on SUSE 10.0 64....help please.

[tutankamon]

Hi everyone, I am trying to get matlab 7 working on SUSE 10.0 64 bits. I read previous posts which have related problems but only with 32 bits version. I'd appreciate any help with this. Thanx in advance. This is the message I am getting:


user@linux:~> /media/dvdrecorder/install -t
cp: cannot stat `/media/dvdrecorder/update/bin/glnxa64/*': No such file or directory
Error writing to /tmp/10487tmwinstall
The installer is unable to copy files to /tmp.
Make sure that /tmp exists, is writable, and has
at least 5 megabytes of available space.
user@linux:~>

???

[mindblast]

  #su root
  type your root password

And try then. /tmp/ exist?

[tutankamon]

Hi. Thanks for the reply.

By the way... /tmp Does exists, and I have set permissions to be written by user.
I have read many posts telling about problems installing matlab7 in SUSE (but 32 bits), and a general recommendation was to install as normal user. (I have tryed both, user-root). And the same problem arises.
Thanks.

[il_ciavo]

I've had the same problem. If you check on your CD archives you'll se that the folder /update/bin/glnxa64/ does not exist. If you know how to get it please post it

[il_ciavo]

run the installer as follows:

./install -glnx86 -nocp

If installing products from multiple CD's, it will be necessary to stop the installation process after each CD by clicking the "Skip CD X" button (where X is the next CD number). This process will then need to be repeat for each of the CD's.

Copy all 3 CD's into a single directory on your local hard drive and then run the installer with the -glnx86 and -nocp flags. Note some files will be overwritten during this process.

Once the installation procedure is complete, the Flexlm License Manager will have to be properly configured. To do this, go to the MATLAB root directory and run the following command:

./install_matlab 4 -glnx86

NOTE: The -glnx86 flag is required for all license manager scripts (lmstart, lmdown, lmstat, etc...) as well as for starting MATLAB.

[roberto07]

my distro is different but i think that problems are common with my matlab 7 release 14:


so: i complete successfully the entire installation procedure but when i try to start the demon license manager before let matlab start the first time, i get this error:

$ /usr/local/matlab7/etc/scripts/lmstart
./etc/scripts/lmstart: line 686: /usr/local/matlab7/etc/scripts/util/setlmenv.sh: No such file or directory

and a similar problem arise when i try to let matlab itself start:
$ /usr/local/matlab7/bin/scripts/matlab
/usr/local/matlab7/bin/scripts/matlab: line 796: /usr/local/matlab7/bin/bin/util/arch.sh: No such file or directory

so i do not understand why the installation procedure inserts that extra "/bin" level which does not exist in fact or that extra "/scripts" in the first case

thank you for any help ...!

[esc2]

my distro is different but i think that problems are common with my matlab 7 release 14:


so: i complete successfully the entire installation procedure but when i try to start the demon license manager before let matlab start the first time, i get this error:

$ /usr/local/matlab7/etc/scripts/lmstart
./etc/scripts/lmstart: line 686: /usr/local/matlab7/etc/scripts/util/setlmenv.sh: No such file or directory

and a similar problem arise when i try to let matlab itself start:
$ /usr/local/matlab7/bin/scripts/matlab
/usr/local/matlab7/bin/scripts/matlab: line 796: /usr/local/matlab7/bin/bin/util/arch.sh: No such file or directory

so i do not understand why the installation procedure inserts that extra "/bin" level which does not exist in fact or that extra "/scripts" in the first case

thank you for any help ...!

I'm using SUSE 10.1. I'm new to this so there may be better ways but this worked for me:
I'm assuming you figured out how to install the single license manager for Matlab 7. From there I used a console (superuser now) to go to /usr/local/matlab7/etc/glnx86 . I put a copy of license.lic in that folder. Now I ran commands in console like ./lmstat , ./lmdiag ... I found out it didnn't like my license syntax. Making a long story short it finally liked "Server localhost ANY 5353" for hostname & hostID.

Now I went to Konsole (user, NOT SUPERUSER) and put a copy of the corrected license file one directory up in /usr/local/matlab7/etc/. From ther in Konsole I ran:
# ./lmdown
# ./lmstart
# matlab

Now matlab7 ran and kept running unless I closed out Konsole.

Good luck.

[praveen2600]

hi

i tried same for my suse 10.0 matlab. after installation i tried to setup flexlm. i ran commond
./install_matlab 4 -glnx86

it ran properly. but when i tried lmstat then output was showing a problem. output is below:

phy15:/usr/local/matlab/etc/glnx86 # ./lmstat
lmstat - Copyright (c) 1989-2003 by Macrovision Corporation. All rights reserved.
Flexible License Manager status on Thu 8/9/2007 19:17

License server status: 5353@localhost
License file(s) on localhost: /usr/local/flexlm/licenses/license.dat:@phy15:license.lic:

lmgrd is not running: Cannot connect to license server (-15,570:111 "Connection refused")
-----------------
I was surprised to see that there was no /usr/local/flexlm/licenses/license.dat file for me. I created /usr/local/flexlm/licenses/ and copied licence.dat and license.lic here

again i tried with lmstat

pathak@phy15:/usr/local/matlab/etc/glnx86> ./lmstat
lmstat - Copyright (c) 1989-2003 by Macrovision Corporation. All rights reserved.
Flexible License Manager status on Thu 8/9/2007 19:51

License server status: 5353@localhost
License file(s) on localhost: /usr/local/flexlm/licenses/license.dat:27000@phy15:license.lic:

lmgrd is not running: Cannot connect to license server (-15,570:111 "Connection refused")

----------------------------------------------------------------------------
License server status: 27000@phy15
License file(s) on phy15: /usr/local/flexlm/licenses/license.dat:

phy15: license server UP (MASTER) v9.2

Vendor daemon status (on phy15):

MLM: The desired vendor daemon is down (-97,121)


Tel me if some body has solution.

[oz]

Hi, praveen2600

You need to start your own thread regarding the problem(s) you are experiencing. This one is too old to be bringing back to the top.

Sorry for any inconvenience...

oz