-
Notifications
You must be signed in to change notification settings - Fork 649
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
build error #658
Comments
More info please. Compiler? OS? Version? Output from cmake? |
I had a similar error building on a mac. If you're on a mac, see my notes at https://github.com/bitshares/bitshares-core/wiki/Building-on-OS-X Also, removing bitshares-core and cloning it again (along with the required 'git submodule update') got me past such errors. Let me know if you are still stuck. |
Hm, that seems to be a common solution. Perhaps we should modify the build documentation to do an out-of-tree build. |
cmake . is OK,but make have error. I build on my mac。
|
In addition, version of your boost library? and OpenSSL library? |
I saw similar errors when I compiled my own boost library instead of using the one from brew. I am guessing that one is using gcc, and another using clang. Are you attempting to compile your own boost or using brew? |
I build with the boost installed with brew without any issue. |
@abitmore i build on my mac . i use boost 1.60 and OPENSSL_VERSION = 1.0.2n
PS: the full log
|
@kenneth I had this happen to me at one point too. I don't have a good answer as to why, but please clone the repository again, and give it another try. That's what I did and the problem disappeared. The error makes it look like fc is using an embedded version of boost, and bitshares is using what you told it to. Somewhere along the line, wires get crossed. If I hazard a guess, I'd say there's a cmake artifact somewhere that we're not deleting before running cmake again. Please let me know the results. |
@jmjatlanta boost version problem ,and i have set BOOST_ROOT but the code always run to boost_1.51
|
@kenneth because there is a |
@abitmore I am out of town at the moment, and my mac is at home (I think that is a crime in some circles). When I return home, I will see if I can adjust the fc build to use the passed-in version of boost instead of the embedded version. @kenneth I will try to recreate the issue. I know I had the same problem, but I don't know if there is a reliable way to fix it. I believe deleting bitshares-core and git clone again is what fixed it for me. |
@jmjatlanta Can you update the fc vendor boost from 1.51 to 1.6? which version boost in you mac.
|
I have attempted to remove the 1.51 version of Boost from bitshares-fc. But there is a requirement for boost::process, which is not officially in boost until 1.64. So it looks like the code that is stored in the bitshares-fc repository is a custom build of the 1.51 version of Boost. Other Bitshares components require Boost versions 1.57 to 1.63, so attempting to move to 1.64 in this library will cause problems elsewhere. There may be other dependencies, as I did not explore beyond boost::process. Therefore, I believe the best near-term solution is to use the Boost version 1.60 installed by brew, and leave the 1.51 version in bitshares-fc. I also believe the longer-term solution is to get Bitshares on newer versions of Boost that include boost::process, and eliminating the 1.51 version stored in the bitshares-fc repository. None of this helps right now with the issue @kenneth sees that I no longer see. As I've said before, I had the same error in the past, fixed it with a sledgehammer, and now cannot recreate it. So it is difficult to diagnose what is going on. What the compiler error indicates: Something (probably a header) has been included as C++, and now something else is attempting to link it, and thinks that the library is C, not C++, and without the required "extern C { }" wrapper, it throws an error. |
@jmjatlanta Thank you for you help ,There is no better way to fix it now。I'll try to change the configuration of my system。 |
If you wish, I published my binaries at the following link: https://github.com/jmjatlanta/bitshares-core/releases/tag/mac-2.0.180226 |
@jmjatlanta Thanks a lot. we env is same but i can't compile pass . |
now i have compile success use boost 1.60 |
Overlooked that you mentioned BTW sorry for the incomplete comment which was sent accidentally. |
@kenneth how did you compile success? i think you use boost 1.60 all the time according your dialogue history,So please tell me what configuration you have changed. |
They say they succeeded, but there's no way. |
I solved this problem with this |
The text was updated successfully, but these errors were encountered: