-
Notifications
You must be signed in to change notification settings - Fork 23
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
HELICS autobuild fails on Linux #13
Comments
@nightlark how exactly do you enable HELICS? The HELICS-Tutorial README mentions compiling from the As an FYI, when I tried building the
|
To build with HELICS support you need to enable the HELICS_EXECUTABLE option. ZMQ should automatically come along with that option when enabled. Which OS version were you building on where you go the errors? It looks like sundials is not being linked properly for some reason. |
If you don't already have a copy of HELICS built that you want to use, there's also an AUTOBUILD_HELICS option that can be set to ON to have cmake download and build a copy as part of the configure step. The HELICS_INSTALL_PATH option can be used to tell cmake where an existing install of HELICS is located. |
Ubuntu 18.04 (using Docker) I created a Sundials is getting automatically downloaded, but I can't tell if it's getting compiled or linked to as part of the build. |
@phlptp any chance you have some ideas here? |
I just tried
on a virtual machine with Ubuntu 18.04, it by default used gcc 7.3 and it built without errors. One possibility is not having suitesparse installed, that might prevent sundials from building built completely. GridDyn can run without it but you might need some other options enabled and it isn't a common use case so I am not sure right now how it would play out in this environment.
and I am not completely sure how that would show up just using cmake .. I guess I usually just use the cmake-gui or ccmake to configure some other options. |
Thanks @phlptp, that's helpful! I'll let you know how my testing goes. |
@phlptp installing
One documented way of fixing this issue is to ensure the Speaking of... below is a screenshot of the cmake curses GUI. Looking at the bottom, I'm curious if |
I have never encountered that particular issue, but if I had to guess I would guess that boost was not installed completely. Based on the location in the fmi library, The FMIGD library, which you could turn off if you didn't need that, uses the boost dll library, which is header only, but it wouldn't surprise me if it had dependencies on Linux. I am just guessing here as I have not encountered that error or any issue with it before. But I also haven't spent that much dealing with FMI stuff on a linux platform either. Now as for Sundials if Suitesparse wasn't available on the first build you may have to change the FORCE_SUNDIALS_REBUILD to ON to get it to build with all the KLU linkages, otherwise GridDyn will probably be kind of slow. |
@phlptp that helped a lot. The trick turned out to be requiring libdl for the FMI library. I edited the
Thanks again for the help! |
I will make the change in the cmake files. |
I tried enabling autobuild for HELICS, and there were a number of errors. It would be good to go over the HELICS and ZMQ find/autobuild scripts to make sure that variable names getting set are correct; different configurations of autobuilding/finding can result in different variables being set.
The text was updated successfully, but these errors were encountered: