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

Enabling APEX causes link errors #2342

Closed
biddisco opened this issue Sep 23, 2016 · 4 comments
Closed

Enabling APEX causes link errors #2342

biddisco opened this issue Sep 23, 2016 · 4 comments

Comments

@biddisco
Copy link
Contributor

I get errors of this kind related to boost regex when I turn on APEX support in HPX

https://gist.githubusercontent.com/biddisco/5e081113df14bc76ed61afdfd47ebae7/raw/745baf6ddada9e71757a304bdac87282d4a025f1/gistfile1.txt

I suspect @khuck is the person to ask about this.

@khuck
Copy link
Contributor

khuck commented Sep 23, 2016

John - Can you post the Cmake options you used? I haven't seen this problem.

Also, are you using the latest HPX? There was a recent change to pull the most recent code from APEX that includes OTF2 support, which has been tested with HPX - but without the communication events.

@biddisco
Copy link
Contributor Author

I'm using master from today. Rechecking everything because I turned off APEX and the link errors didn't go away, so maybe some other option I used is the problem.

@hkaiser
Copy link
Member

hkaiser commented Sep 23, 2016

@biddisco Please verify that libhpx.so is being linked against the correct version of the Boost.Regex library.

@biddisco
Copy link
Contributor Author

Please accept my apologies - it turns out to be a problem that is caused when you allow HPX to set the build flags, if I explicity force CMAKE_CXX_FLAGS=-std=c++11 then things build ok, but if I do not use that flag, HPX must set some c++14 flags and the link problems appear - I would guess that there is some #define in boost that is causing problems because I tried building boost with c++14 and hpx with c++14, but that didn't work.

I will investigate this further when I have more time, for now I will close this issue.

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

No branches or pull requests

3 participants