Skip to content
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

OMNeT++ 5.1 compatibility w/ Windows 64 bits #27

Closed
gabrielbiasi opened this issue Apr 26, 2017 · 5 comments
Closed

OMNeT++ 5.1 compatibility w/ Windows 64 bits #27

gabrielbiasi opened this issue Apr 26, 2017 · 5 comments

Comments

@gabrielbiasi
Copy link

I found some problems when trying to compile veins on Windows 64 bits and OMNeT 5.1 after the commit b96ba50:

'make MODE=release all
make[1]: Entering directory '/c/omnetpp-5.1/workspace/veins/src'
Creating shared library: ../out/gcc-release/src/libveins.dll
.tmplib4768(TraCIConnection.o):TraCIConnection.cc:(.text+0x145): undefined reference to '__imp_closesocket'
(... a lot lines hidden ...)
.tmplib4768(TraCIScenarioManagerForker.o):TraCIScenarioManagerForker.cc:(.text+0x1854): undefined reference to '__mp_WSAStartup'
collect2.exe: error: ld returned 1 exit status
make[1]: *** [Makefile:170: ../out/gcc-release/src/libveins.dll] Error 1
make[1]: Leaving directory '/c/omnetpp-5.1/workspace/veins/src'
make: *** [Makefile:12: all] Error 2`'

I think it's probably the missing link from the socket communication library, so I simply solved this problem adding the parameter -lws2_32 to the makemake configuration.
I hope this help some windows users to enjoy their simulations in 64 bits now.

@riebl
Copy link
Contributor

riebl commented Apr 26, 2017

Have you been able to compile Veins using Windows 64bit and OMNeT++ 5.1 before commit b96ba50? I suppose this issue is not caused by aforementioned commit but a "side effect" of OMNeT++ 5.1.

@gabrielbiasi
Copy link
Author

gabrielbiasi commented Apr 26, 2017

I've tried and failed too. I am not saying that exactly your commit caused the error, sorry if it sounded that way.
I think that the change of the new toolchain and libraries for mingw64 in OMNeT++ 5.1 is probably the case.

@riebl
Copy link
Contributor

riebl commented Apr 27, 2017

No offence taken. I have just been curious if you succeeded without this commit :-)

@ChenKangQiang
Copy link

ChenKangQiang commented May 31, 2017

Is it using command ./configuremake -lws2_32. In my machine,it still doesn't work. My GCC is TDM-GCC-64.

@gabrielbiasi
Copy link
Author

Solved by e13b642.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants