-
Notifications
You must be signed in to change notification settings - Fork 758
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
update to boost-1.55 #993
update to boost-1.55 #993
Conversation
Hi tim - thanks for this. Build fails for me on ubuntu 13.04. I don't understand the "new_allocator"-related error, though I can't see any specific compiler requirements in the boost 1.55 docs, so do you know if this is a bug or an expected issue? Excerpt from failed build: http://pastie.org/8473057
(I used ccache too) EDIT: Aha, boost requirments here say this compiler should indeed be supported. |
I get this error on OSX: [ 43%] Building CXX object lang/CMakeFiles/libsclang.dir/LangSource/SC_TerminalClient.cpp.o |
Thanks tim for the fixes. I get successful build now. I don't get @bagong 's error - but that's probably because I'm on linux where system_timer.hpp is in my system path. There are a few files that this PR drops so there may potentially be others to add in. |
If I copy system_timer.hpp into the respective folder, it builds successfully... |
Should we merge this? |
Does it work as-is on mac? The messages from @bagong suggest that at least one change is needed. The update would be good in general - I don't know if Tim had any specific motivations but it seems there are some improvements in the "atomic" stuff, plus some "asio" stuff that may help windows devs. So if build is fine then yes let's go... |
I haven't tested it yet, but it might be a good idea to update everything we can in terms of external libraries in a short period – we can then get up to date and not worry for a while then. So QT5 seems to be working, maybe there are other things? |
Julian - thanks for doing a lot of tidying up recently, by the way! For this particular PR, I think it could well be confusing if we merge it before checking that mac people can build it. Could a Mac user please check it out and check it? If there is any problem with
I believe that the things we use are already dragged in by |
I have built successfully in the past with boost 1.5.5, but now I get an error in a very early build stage. Maybe has to do with the latest Mac toolchain? I also get an error with supernova others don't have. However, this is my error:
|
related to apple's latest compiler. use apple's clang-5.0 instead of 5.1 or wait for boost-1.56. |
Homebrew provides a version 1.55.0_1, which seems to be patched for that particular problem. The build goes through with it. Is it an option too to use that, or are there customizations in SC's bundled boost? |
there are some additions to boost.lockfree, that did not make it into that boost release |
Compiles fine on OSX 10.8 here, too. |
… ups, not sure: I was referring to c7600cc |
@telephon you can test this branch by doing
and then build etc |
@danstowell this is useful and non-trivial information. |
@telephon thanks. I just copied-and-pasted it from this github page ;) but it probably wasn't obvious if you're looking at it via the emails. No I don't think we should add in the file, because that means altering the boost library and making it different from the "upstream". I'll merge, make the change, and hope that this is the correct way to deal with that issue! |
On 27 Mar 2014, at 18:24, danstowell notifications@github.com wrote:
|
I overlooked you removal of the include, but still... |
including the main asio header should be enough. if the file was removed from boost-1.55 it would explain, why it wasn't picked up by bcp and left out of the extraction process. |
@bagong why should that be? |
Well, the error I posted above occurres with with the latest toolchain. I mean of course there are workarounds... I am not protesting, just wondering... |
Maybe related? jonathantopf commented 11 days ago:
|
Well, as far as I understand the idea is to use bundled boost. As Tim said there are some differences. And a side problem is that the supernova compile get's an error if you use a boost from the system. Maybe some paths can only be resolved relative to the sc-repo. |
Looks more like an issue how to organize version control and workflow ;) Scott Carver is already suggestion a solution on the sc-dev list. It seems to be a well known issue (and yes, probably the one you're referring to. that must be how 1.55.0_1 came about, with which I built successfully, except for supernova...)... |
@bagong sorry, I think I thought that tim's apple patch fixed your issue. Will continue discussion on the list |
@danstowell Yes, I sort of gathered that... Sorry for sloppy language, it's not easy to be clear sometimes. |
No description provided.