Comment 8 for bug 1694926

------- Comment From <email address hidden> 2017-06-20 09:49 EDT-------
(In reply to comment #4)
> The Boost packaging currently excludes s390x support for Boost.Context and
> Boost.Coroutine; These are required to support Ceph >= 12.0.3.
>
> Working around this by disabling the beast frontend for rgw in ceph (inline
> with upstream ceph commits); however would be good to get these functional
> on s390x as well.
>
> I do not believe these modules have been ported to s390x upstream.
>
> Boost Context need porting upstream:
> http://www.boost.org/doc/libs/1_64_0/libs/context/doc/html/context/
> architectures.html
>
> Coroutine depends on Context.
>
> This needs to be fixed upstream.
>
> Can you elaborate as to what "beast frontend for rgw" is?
>
> Emailed IBM contacts asking if anybody can look into porting Boost Context
> to s390x.
>
> The 'beast frontend' is a new HTTP frontend for the Rados Object Gateway
> base on async io, rather than the current default which is fastcgi.
>
> This is all quite new still, so its not the default.
>
> according to:
> https://github.com/ceph/ceph/blob/master/debian/rules#L25
> https://github.com/ceph/ceph/commit/25d794d98a68134f8097ed434909822ded0425df
> initial porting seems to be required

Porting Boost.Context to s390x probably can be based on the Glibc setcontext/getcontext .... stuff. From a first glance this should not be toooo much effort. We will try to cover this in the toolchain team. As I understand it it does not appear to be super-urgent since the default implementation keeps working for S/390?!