omnet++ 5.0 installation on Ubuntu Gnome 16.04: Path Variable not recognized
1,179 views
Skip to first unread message
Christian Arendt
May 14, 2016, 11:23:22 AM5/14/16
to OMNeT++ Users
Dear Omnet Community,
I have a problem installing omnet on Ubuntu Gnome 16.04. After installing the prerequisites I issued the . setenv command and then ran ./configure as I used to before, but configure tells me that the omnetpp-5.0/bin is not in the PATH and so does make. I tried every possibility I know to set the PATH variable (configure .profile, .bashrc, etc/environment, use the export command, ...) but nothing worked. I also tried to comment the PATH check out in the makefile, then make runs but as soon as I want to start omnet then I get an error. I also tried to use the older omnet-4.6, which worked for me on ubuntu 14.04 based distros before, but with the same result.
This is the output at the end of ./configure:
WARNING: The configuration script could not detect the following packages:
MPI (optional) Akaroa (optional)
Scroll up to see the warning messages (use shift+PgUp), and search config.log
for more details. While you can use OMNeT++ in the current configuration,
be aware that some functionality may be unavailable or incomplete.
WARNING: your PATH doesn't contain /home/christian/software/omnet/omnetpp-5.0/bin!
Add the following line to your .profile or .bash_profile (provided you use bash):
export PATH=$PATH:/home/christian/software/omnet/omnetpp-5.0/bin
I noticed that with Ubuntu 14.04 I didn't get the Warning that MPI is missing, but I did not find the right package that ./configure wants to have. is this related to my issue?
Is this a known issue with the new ubuntu 16.04.? Is there a workaround for that?
Many Thanks in Advance
Regards
Christian
I have a problem installing omnet on Ubuntu Gnome 16.04. After installing the prerequisites I issued the . setenv command and then ran ./configure as I used to before, but configure tells me that the omnetpp-5.0/bin is not in the PATH and so does make. I tried every possibility I know to set the PATH variable (configure .profile, .bashrc, etc/environment, use the export command, ...) but nothing worked. I also tried to comment the PATH check out in the makefile, then make runs but as soon as I want to start omnet then I get an error. I also tried to use the older omnet-4.6, which worked for me on ubuntu 14.04 based distros before, but with the same result.
This is the output at the end of ./configure:
WARNING: The configuration script could not detect the following packages:
MPI (optional) Akaroa (optional)
Scroll up to see the warning messages (use shift+PgUp), and search config.log
for more details. While you can use OMNeT++ in the current configuration,
be aware that some functionality may be unavailable or incomplete.
WARNING: your PATH doesn't contain /home/christian/software/omnet/omnetpp-5.0/bin!
Add the following line to your .profile or .bash_profile (provided you use bash):
export PATH=$PATH:/home/christian/software/omnet/omnetpp-5.0/bin
I noticed that with Ubuntu 14.04 I didn't get the Warning that MPI is missing, but I did not find the right package that ./configure wants to have. is this related to my issue?
Is this a known issue with the new ubuntu 16.04.? Is there a workaround for that?
Many Thanks in Advance
Regards
Christian
Michael Kirsche
May 19, 2016, 5:17:28 AM5/19/16
to OMNeT++ Users
Dear Christian,
last Ubuntu 16.04 machine that I've set up, worked just fine.
I usually export the OMNeT paths via .bashrc, after setting the path and logging out / in again, check (echo $PATH) that the path is set correct. Don't know why it shouldn't work...
Regards,
Michael
last Ubuntu 16.04 machine that I've set up, worked just fine.
I usually export the OMNeT paths via .bashrc, after setting the path and logging out / in again, check (echo $PATH) that the path is set correct. Don't know why it shouldn't work...
Regards,
Michael
Reply all
Reply to author
Forward
0 new messages