[Bug 2060108] Comment bridged from LTC Bugzilla

[bugproxy]

------- Comment From bergner at us.ibm.com 2024-04-09 13:07 EDT-------
(In reply to comment #5)
> I've asked in the upstream issue for the preprocessed source file that I can
> recreate and debug with.

I was able to create a small reproducer myself.  I'll have a look.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to python-greenlet in Ubuntu.
https://bugs.launchpad.net/bugs/2060108

Title:
  greenlet 3.0.3 fails to build on ppc64el (and riscv64)

Status in greenlet:
  New
Status in The Ubuntu-power-systems project:
  Triaged
Status in python-greenlet package in Ubuntu:
  New

Bug description:
  greenlet 3.0.3 fails to build on riscv64 and ppc64el:

  complete build logs at
  https://launchpad.net/ubuntu/+source/python-greenlet/3.0.3-0ubuntu2

  riscv64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
  -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fno-
  omit-frame-pointer -ffile-prefix-map=/<>=. -fstack-protector-strong
  -Wformat -Werror=format-security -fdebug-prefix-
  map=/<>=/usr/src/python-greenlet-3.0.3-0ubuntu2 -Wdate-time
  -D_FORTIFY_SOURCE=3 -fPIC -I/usr/include/python3.11 -c
  /<>/src/greenlet/greenlet.cpp -o build/temp.linux-
  riscv64-cpython-311/<>/src/greenlet/greenlet.o -Os

  So the reason is that recent Linux distros decided to build with -fno-
  omit-frame-pointer by default. Apparently both the riscv64 and the
  ppc64el implementations cannot cope with that.

  The issue can be reproduce by adding -fno-omit-frame-pointer to the
  build flags.

  https://launchpad.net/ubuntu/+source/python-greenlet/3.0.3-0ubuntu4
  _____

  There is also this upstream github issue:
  https://github.com/python-greenlet/greenlet/issues/395

To manage notifications about this bug go to:
https://bugs.launchpad.net/greenlet/+bug/2060108/+subscriptions