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

OS X Support #33

Closed
git-patrick opened this issue Jun 1, 2015 · 7 comments
Closed

OS X Support #33

git-patrick opened this issue Jun 1, 2015 · 7 comments

Comments

@git-patrick
Copy link

I'm trying to get boost fiber to work on OS 10.10.4. The first issue I had was the OS X version of Clang doesn't support thread_local for some reason. I was considering switching fiber over to boost thread local storage instead of using thread_local, but I figured I would just try just using GCC-5.1.0 and link with stdlibc++ instead.

Building boost modular and boost fiber was successful, and building the fiber example "simple.cpp" was also successful, but it fails with segmentation faults. Any idea what's going on?

Maybe I'll hack it to use boost thread local storage so the standard clang will work instead..

@olk
Copy link
Member

olk commented Sep 27, 2015

until Apple adds support for thread_local it will not work - sorry

@olk olk closed this as completed Sep 27, 2015
@Rydgel
Copy link

Rydgel commented Feb 13, 2017

@olk Apple added support for thread_local since last Xcode.
It now compiles fine, but gives some segfaults deep inside boost context.

I can provide more informations if needed.

@olk
Copy link
Member

olk commented Feb 13, 2017

@Rydgel yes, but report in boost.context please

@Rydgel
Copy link

Rydgel commented Feb 14, 2017

This is actually this bug boostorg/context#38
So I guess I'll just wait the next Boost release.

@olk
Copy link
Member

olk commented Feb 14, 2017

@Rydgel could you verify that the code is working, please - I don't own a Mac, so I can't test it

@Rydgel
Copy link

Rydgel commented Feb 14, 2017

@olk just recompiled Boost with the patch from that context issue. Everything is working now!

@olk
Copy link
Member

olk commented Feb 14, 2017

@Rydgel ty

@jxfwinter jxfwinter mentioned this issue Jun 25, 2018
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