|
|
#11
27-Feb-2009, 22:26
|
|||
|
|||
Re: Problem executing nam-1.13[quote=RodolfoAlvizu]problems with the Spanish...[;/quote]Well, I don't have much Spanish, but I think all of those avisos are warnings, not errors. At least that's my impression.
However, here's the real problem (I think): Quote:
http://www.gidforums.com/t-20442.html Scroll down to the last entry (my post number 9) where I explain what the problem is. Here's the solution that I recommend: Navigate to the nam-1.13 directory. Enter the following commands Code:
Regards, Dave Last edited by davekw7x : 27-Feb-2009 at 23:06.
|
|||
|
#12
28-Feb-2009, 07:37
|
|||
|
|||
Re: Problem executing nam-1.13You was rigth Dave... It presents a new error...
[root@rodolfopc bin]# namthanks^n |
|
#13
28-Feb-2009, 09:44
|
|||
|
|||
Re: Problem executing nam-1.13Quote:
My suggestion for any install of ns: 1. Delete or rename the ns-allinone-2.33 directory tree where you have been doing your work. This is really important: start with a brand new fresh installation. 2. Unzip ns-allinone-2.33.tar.gz to wherever you want it to be. You put it in /opt, so the rest of this narrative is based on that location. I don't recommend any particular location, but /opt is as good as any. 3. If your ns-allinone-2.33 directory is somewhere that requires root permission then change permissions so that you (a normal user, not root) can work on it. My user name is dave and my user group is dave so do an "su" to become root, then Code:
Now log in as a normal user (not root). If you have logged into the desktop (kde or gnome) as root. Then STOP. Log out and log back in as a normal user. You don't have to reboot, just log out and in. See Footnote. If you unzipped the ns file in /opt, then execute the following: Code:
Code:
When the install process finishes, hit ctrl-c in the "tail" window. Open install.log with a text editor and look for stuff like: Code:
Just in fromt of most of the banner lines (all of those "===="), there will be something to the effect that the previous build was successful. Or there may be some kind of failure message. The actual cause of the failure may be in some lines before the banner line. Regardless of errors in the build process, it proceeds to the next. (That's why I alway capture everything in a file like install.log) Note that there may be many, many compiler warnings and other compiler messages. Unless it specifically gives a message that the build failed, you can ignore them for now. The last build banner is Code:
In your case, it will probably report a failure and I already showed how to get around that. If there are any other failures, you must fix them now. In my case (32-bit Centos 5), nam succeeded and near the bottom of the install log I see Code:
If yours is different (other than the line about nam), then stop right here. Fix it. If you have made the changes to PATH and the other environmental variables in .bashrc and you have confirmed their values, then go to your home directory and invoke ns: Code:
If it gives the ns prompt '%', then exit from ns Invoke nam: Code:
If you get this far, then I highly recommend the following: Cd to the ns-2.33 directory and execute the validation command Code:
This takes a verrrrrry loooooong time. Again, you can open another terminal window, navigate to the ns2-33 directory and execute Code:
When it finishes, you can inspect the validate log file to see whether there were any unexplained failures. There will be something over 6,000 lines in the validate log. Regards, Dave Footnote: My personal recommendation is that you should never (that's never) log into the desktop as root. You can execute commands as root when you need to, but don't log in as root. Period. I concede that this advice is based on personal experience and my recommendation is only an opinion. Everyone has a right to his/her opinion and I respect the right for anyone and everyone to have opinions that are different from mine. Last edited by davekw7x : 28-Feb-2009 at 10:49.
|
|
#14
28-Feb-2009, 11:54
|
|||
|
|||
Re: Problem executing nam-1.13Thanks Dave, I did all wath you say as user...
But when invoke nam got the same error: [rodolfo@rodolfopc ~]$ namI don't see other error msg, but there are many things that seems to be wrong. I post the buil nam an the rest of the install.log: ================================================== ==========I Don't execute the validation yet, becouse still the problem... |
|
#15
28-Feb-2009, 13:16
|
|||
|
|||
Re: Problem executing nam-1.13Quote:
So, you deleted all of the old stuff and unzipped ns-allinone-2.33.tar.gz in /opt, right? By the way, where did you get ns-allinone-2.33.tar.gz? If you do a "ls -l ns-allinone-2.33.tar.gz" what do you see? It should show the size to be exactly 55428314 bytes. Now for your report: OK. Out of all of that install.log, here is the significant part. This starts about 324 lines below the Build nam-1.13 banner: Code:
If you started with a new distribution, there will be no executable "nam" program anywhere under /opt/ns-allinone-2.33. Are you telling me that you executed "nam" at this point and you got a message like the following? Code:
Execute the following: Code:
What does it say? From /opt/ns-allinone-2.33 execute Code:
What does it say? Or, after the install failed, did you go into the nam-1.13 directory and do the configure and make procedure that I showed you (in my post number 11 in this thread) for nam? Quote:
Did that succeed? Where was the "nam" executable when it finished? Regards, Dave |
|
#16
28-Feb-2009, 13:33
|
|||
|
|||
Re: Problem executing nam-1.13Don't remember where I got the ns-allinone-2.33.tar.gz because it was 17 days ago!
Quote:
Yes, after the install failed, I go into the nam-1.13 directory and do the configure and make procedure that you showed me... I found this,http://forums.fedoraforum.org/showthread.php?t=206795 it's that right? |
|
#17
28-Feb-2009, 14:14
|
|||
|
|||
Re: Problem executing nam-1.13Quote:
I have no way of testing Fedora Core 10. The reason that I stopped using Fedora for serious (time-sensitive) work and the reason that I stopped using 64-bit Linux distributions for serious (time-sensitive) work is that there are just too many little gotchas that come from newer packages (gcc, tcl/tk, etc.) or newer applications with incompatible driver and/or library requirements. I couldn't even get my video working with Fedora Core 10. Sometimes I like to mess with this kind of stuff because I have found that, for me, the best way to learn how stuff works is when it doesn't work and I have to dig into it. I just don't have the spare time or stamina to fight with Fedora Core 10 just now. Sorry. Regards, Dave "Over and out." |
|
#18
28-Feb-2009, 15:52
|
|||||
|
|||||
Re: Problem executing nam-1.13Well, the final point for the installation was in the link that show you. And I did all the process again.
For future reference ns-allinone-2.33 64-bit fedora 10; 1. Delete or rename the ns-allinone-2.33 directory tree where you have been doing your work. 2. Unzip ns-allinone-2.33.tar.gz to wherever you want it to be. You put it in /opt, so the rest of this narrative is based on that location. I don't recommend any particular location, but /opt is as good as any. 3. If your ns-allinone-2.33 directory is somewhere that requires root permission then change permissions so that you (a normal user, not root) can work on it. My user name is rodolfo and my user group is rodolfo so do an "su" to become root, then Code: Quote:
4. Go to the link below and download the second patch. Then copy the patches in tk8.4.18 directory. http://bugs.gentoo.org/show_bug.cgi?id=225999 Code: Quote:
5. Now log in as a normal user (not root). If you unzipped the ns file in /opt, then execute the following: Code: Quote:
6. Navigate to the nam-1.13 directory. And enter the following commands Code Quote:
7. Made the changes to PATH and the other environmental variables in .bashrc. then go to your home directory and invoke ns. Most apear %. Then invoke nam, and the nam window opens. close it. If you get this far, then: Cd to the ns-2.33 directory and execute the validation command Code: Quote:
F.N: I made this reply while executing the validation proces and I finished first. Thank you very much dave!!! |
|
#19
28-Feb-2009, 16:14
|
|||
|
|||
Re: Problem executing nam-1.13From the validation
Quote:
|
|
#20
28-Feb-2009, 16:17
|
|||
|
|||
Re: Problem executing nam-1.13Quote:
I really appreciate your reporting of the fix. I'm guessing that your work will help other people, and that's what it's all about, right? Regards, Dave "What goes around, comes around..." ---Anonymous |
Recent GIDBlog
Toyota - 2009 May Promotion by Nihal
| Thread Tools | Search this Thread |
| Rate This Thread | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| VC++ 2008 : problem in executing and running C codes | Ndimangwa | C Programming Language | 2 | 03-Feb-2009 14:55 |
| Visual Studio .NET 2003 problem in executing C source files | Debugger1 | C Programming Language | 15 | 03-Feb-2009 04:32 |
| Problem installing nam 1.13 | sagarnatekar | Computer Software Forum - Linux | 3 | 22-Jan-2009 20:26 |
| Problem Executing Program Via command prompt: Windows vista | Relay | C Programming Language | 5 | 09-Mar-2007 13:57 |
| Problem with executing PHP in webpage | fdgloworm | Apache Web Server Forum | 0 | 13-Feb-2006 12:43 |
Network Sites: GIDNetwork · GIDWebHosts · GIDSearch · Learning Journal by J de Silva, The
