-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simu5G build crash on Omnet++ 6.0, Build id: 220413-71d8fab425 and INET 4.3.9 #48
Comments
Hello, latest stable release of Simu5G (1.2.0) requres OMNeT++ 6.0pre11 and INET 4.3.2 (see here). However, the master branch in GitHub has just been updated to support OMNeT++ 6.0 and INET 4.3.9. So if you want to try with those, then please download the version of the code available in the current master branch from GitHub. |
Unfortunately the master branch also doesn't build without errors. I'll give it a try with OMNeT++ 6.0pre11 and INET 4.3.2 Description Resource Path Location Type |
Simu5G-1.2.0 fails to build also with omnetpp-6.0rc2 and inet-4.3.7 Building with inet-4.3.2 was successful but building inet-4.3.2 itself lead to a lot of warnings |
On Linux (Ubuntu) it works straight forward (just tested it right now): Example for Building and Using Simu5G (master branch)
Tested on: Ubuntu Linux Desktop 22.04 LTS However, based on your screenshot, I assume that you are working on Windows. I am not sure to what extent Simu5G has been tested on Windows, since I use it on a Linux system only. However, what you could do if you do not run Linux on your simulation machine, is to install it in an VM (e.g. virtualbox). |
I replicated your configuration in a virtual box VM and the simulations work fine now INET showed a bunch of warnings at build time but this didn't seem to impact the simulations Thanks for the heads up! There is no information on Simu5G website that it should be run only with Linux or that Windows isn't supported. Maybe this should be mentioned there. |
No problem - good to hear. The "no such parameter" warnings are meaningless and can be ignored (as far as I know) - the IDE fails to detect that the mentioned parameter is correctly used, often due to wildcards. |
Latest master branch works fine with OMNeT++ 6.0 on Windows using the Windows Subsystem for Linux. We have not tested it with the MinGW environment yet. Older versions - that is, Simu5G v1.2 - worked fine on Windows using the MinGW environment. |
I already had installation issues with OMNeT++ 6.0 on WSL and GUI problems that made me sorry to go down this road. Simu5G v1.2 can't be built without errors on Windows on the exact configuration mentioned on http://simu5g.org/ as I already mentioned before. The only way that looks kind of stable is to use a Linux VM on Windows and run it there. |
In my own (little) experience on Windows, I made Simu5G v1.2 work by recompiling OMNeT++ using GCC instead of CLANG... that is, by setting BTW, a VM with Linux is of course a good compromise :) |
Cool, I'll give it a try. So far I got it to work also with WSL + Ubuntu and xfce but I still need vcxserver |
Which version of Omnet did you use? |
As I said above:
|
For building on Windows, refer to #65, which should solve the problem |
Hi guys,
I'm trying to use Simu5G on my Omnet++ setup and the build crashes every time:
Anybody have any ideas how to debug it?
Thanks
Bogdan
Console:
"fatal error: too many errors emitted, stopping now [-ferror-limit=]
12 warnings and 20 errors generated.
make[1]: *** [Makefile:420: ../out/clang-debug/src/apps/mec/MecApps/MecRequestBackgroundGeneratorApp/MecRequestBackgroundGeneratorApp.o] Error 1
19 warnings and 20 errors generated.
12 warnings and 20 errors generated.
make[1]: *** [Makefile:420: ../out/clang-debug/src/apps/mec/MecApps/MecRequestForegroundApp/MecRequestForegroundApp.o] Error 1
make[1]: *** [Makefile:420: ../out/clang-debug/src/apps/mec/WarningAlert/MECWarningAlertApp.o] Error 1
make[1]: Leaving directory '/c/Users/Bogda/Documents/omnetpp-6.0/samples/Simu5G-1.2.0/src'
make: *** [Makefile:2: all] Error 2
"make MODE=debug -j12 all" terminated with exit code 2. Build might be incomplete.
12:45:00 Build Failed. 141 errors, 194 warnings. (took 18s.841ms)"
The text was updated successfully, but these errors were encountered: