Your e-mail messages will be slightly edited before being posted here :-) Ljiljana. Messages will be posted in a reverse chronological order (last message listed first) and grouped by the subject matter. ****************************************************************************** -------- Original Message -------- Subject: ENSC 427 Assignment #6 problem Date: Sat, 6 Mar 2010 23:45:02 -0800 (PST) From: Eric Boyer To: ljilja@cs.sfu.ca Hi professor. I am having a problem with the OPNET tutorial for assignment #6. I have created the process model, but when I compile it, the compilation fails and the error that is returned is "/usr/ucb/cc: language optional software package not installed". I read about this problem online and found that it means that there is no C compiler installed. I am running OPNET remotely from my Mac through X11. Any idea how to solve this issue? -Eric ___________________________________________ From: "Gary Hall via RT" Subject: [fas.sfu.ca #111912] [Fwd: ENSC 427 Assignment #6 problem] Date: Sun, 7 Mar 2010 10:33:20 -0800 To: ljilja@fas.sfu.ca CC: ejb3@sfu.ca, lsa38@sfu.ca Eric, What is the (fully qualified) name of the machine on which you are attempting to run the compile? If is is machine on FASnet, (e.g., .ensc.sfu.ca, .fas.sfu.ca, .cs.sfu.ca, etc), it would be better to use the Gnu compiler in /usr/local/bin/gcc. Make sure /usr/local/bin is in your command path and /usr/local/lib is in your LD_LIBRARY_PATH. You can use 'echo' to check: % echo $PATH % echo $LD_LIBRARY_PATH If they don't appear in the respective lists, you can add them before running the compile: E.g., for CSH: % setenv PATH /usr/local/bin:$PATH % setenv LD_LIBRARY_PATH /usr/local/lib:$LD_LIBRARY_PATH These commands can be added to your startup script (.login or .mylogin) somewhere after the first paths have been added to the respective variables. Gary -- Gary Hall, Software Consultant Network Support Group, Faculty of Applied Science Room: L 9009, Phone: (778) 782-5925, Fax: (778) 782-5404 ****************************************************************************** Date: Mon, 25 Jan 2010 16:55:17 -0800 (PST) From: Reza Qarehbaghi To: Ljiljana Trajkovic Subject: A solution for problem in remotely connecting to server. Dear Prof. Trajkovic, Some students have some problems in remotely connecting to server, because all ports of "vncserver" are dedicated and there is no more ports for them to connect. The problem is every time that students run "vncserver" command, they recieve an extra port to communicate with server and that is why there is no other port available. I add one more step to the remote login instructions to avoid this problem in future. Please add this step to "Remote login from windows machines using PUTTY and VNC viewer" and also send to ENSC427 students to kill their extra ports. This step can be added after step 4 as step 5. "This port is dedicated to you and you can always use this port to connect to server. If you ran this command more than one time and you have more than one dedicated port, you should kill all of them exept one that you need it to connect to server. You can go to (/ensc/grad1/[username]/.VNC) folder to see the ports that are dedicated to you. To kill extra ports, in putty window, run "vncserver -kill :[portnumber]. This can help others to have access to server remotely." Sicerely Yours, Reza Qarehbaghi ****************************************************************************** ******************************************************************************