Boost.Context and Boost.Coroutine not built on s390x

[James Page]

The Boost packaging currently excludes s390x support for Boost.Context and Boost.Coroutine; These are required to support Ceph >= 12.0.3.

[James Page (james-page)]

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.

[Dimitri John Ledkov (xnox)]

I do not believe these modules have been ported to s390x upstream.

[Dimitri John Ledkov (xnox)]

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.

[Dimitri John Ledkov (xnox)]

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.

[James Page (james-page)]

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.

[Frank Heimes (fheimes)]

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

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-06-20 03:25 EDT-------
The Boost packaging currently excludes s390x support for Boost.Context and Boost.Coroutine;
These are required to support Ceph >= 12.0.3.

[bugproxy (bugproxy)]

------- 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?!

[Dimitri John Ledkov (xnox)]

Correct, this is not super-urgent. It is a nice to have. Current total list of packages that could use boost context / coroutine is rather small:

Reverse-Build-Depends
=====================
* ceph
* hhvm
* kicad

[Dimitri John Ledkov (xnox)]

Looking at https://www.boost.org/doc/libs/1_68_0/libs/context/doc/html/context/architectures.html I still do not see boost-context support for s390x.

Has there been any progress w.r.t. to this in the toolchain team at IBM?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2019-11-29 07:58 EDT-------
Boost Context support has been implemented as part of the OpenMainframeProject:

https://github.com/boostorg/context/pull/117

It should be available with Boost 1.72.0

[Dimitri John Ledkov (xnox)]

I can't remember if ceph has a vendored copy of boost or not. So reopening that task as well.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2019-11-29 10:15 EDT-------
Re-opened also in Bugzilla

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2019-12-10 07:54 EDT-------
Changed Target to Ubuntu 20.04. Please integrate

[Launchpad Janitor (janitor)]

This bug was fixed in the package boost1.71 - 1.71.0-4

---------------
boost1.71 (1.71.0-4) unstable; urgency=medium

  [ Giovanni Mascellani ]
  * Transition to the Salsa CI team pipeline.
  * Enable -context on mips64el (closes: #948015).
  * Set graph-parallel test as flaky until
    https://github.com/boostorg/graph_parallel/issues/21 is resolved.
  * Compile test context/demo1.cpp only on amd64, because it uses some
    architecture specific instructions.

  [ Dimitri John Ledkov ]
  * Add chrono to thread autopkgtest until
    https://github.com/boostorg/boost_install/issues/27 is resolved.

 -- Giovanni Mascellani <email address hidden> Fri, 10 Jan 2020 14:26:58 +0100

[James Page (james-page)]

To late to enable this for focal - will do so in 'g'

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-04-24 04:00 EDT-------
IBM Bugzilla status-> closed, Fix Released by all requested distros

[Launchpad Janitor (janitor)]

This bug was fixed in the package ceph - 15.2.5-0ubuntu1

---------------
ceph (15.2.5-0ubuntu1) groovy; urgency=medium

  [ Corey Bryant ]
  * d/control: Remove Breaks/Replaces that are older than Focal (LP: #1878419).
  * d/p/enable-strsignal.patch: Enable HAVE_REENTRANT_STRSIGNAL for groovy
    to fix FTBFS with glibc 2.32.
  * d/p/rules: Enable RelWithDebInfo (LP: #1894453).

  [ James Page ]
  * New upstream point release (LP: #1898200).
  * d/p/fix-crash-in-committed-osd-maps.patch: Drop, included upstream.
  * d/p/*: Refresh.
  * d/libcephfs-dev.install: Drop ceph_statx.h.

  [ Dimitri John Ledkov ]
  * d/rules,control: Enable boost context usage on s390x (LP: #1694926).

 -- James Page <email address hidden> Tue, 06 Oct 2020 12:01:52 +0100