Why might mcc begin hanging on two different machines from one week to the next.

The machines in question are Centos 5 and Centos 6, x86_64. They are physical machines.

Matlab was recently installed on both, with a 1 yr license. I am a new compiler user.

Last week I used mcc extensively while working on build files. Everything was fine.

Today I cannot run a build or even 'mcc -help' on either machine. 'mcc -help' results in the script hanging and never returning, just as an attemped build does.

Nothing has changed with the matlab code base or with the configuration of either machine. These are standalone machines whose network connections can see the outside world.

Any clues on where to look?

[Walter Roberson]

Could you experiment with turning off their anti-virus, and experiment with turning off their built-in firewall ?

[Bruce]

No anti virus running on either machine.

Did:

service iptables stop
chkconfig --del iptables

The centos5 machine had iptables running, the centos6 machine did not. After stopping iptables on cents5, got same result, i.e. mcc command hangs.

Thanks.

Answer 1

[Bruce]

Solved my own problem. Figured it was completely unrelated but was not.

I migrated to a new laptop over this period. I build on linux machines via the iTerm2 app on the new mac laptop. While XQuartz did migrate, I found that it wouldn't start properly. Once I re-installed XQuartz, the mcc compile will now behave as expected. Who would've thought...

b