How to use manylinux_2_34?

[agarny]

Hi,

I have a C++-based project that relies on various third-party libraries. On Linux, everything is built on Ubuntu 22.04. When it comes to Python bindings, I use nanobind and it's all working fine.

However, now, I want to use cibuildwheel to get Python weels for my project and this is where I am having problems. I am getting undefined references for both __libc_single_threaded and mallinfo2.

It all used to be fine when I was building things on Ubuntu 20.04, but that version of Ubuntu is now a bit old and I would like to support Ubuntu 22.04 and later.

I am using cibuildwheel 2.22.0 with manylinux_2_28, but I understand that this version of manylinux is not recent enough for my needs? It looks like I need at least manylinux_2_34 (see here), but again it looks like manylinux_2_34 didn't make it in time for cibuildwheel 2.22.0 (see here).

So, assuming I have got things right (?), what are my options?

Cheers, Alan.

[agarny]

Ok, I hadn't thought of it, but I was using the following in my GitHub workflow:

- name: Build Python wheels
  uses: pypa/[email protected]
  env:
    CIBW_ARCHS: auto64
    CIBW_BUILD: 'cp*'
    CIBW_ENVIRONMENT_MACOS: MACOSX_DEPLOYMENT_TARGET=13.0
    CIBW_MANYLINUX_X86_64_IMAGE: manylinux_2_34
    CIBW_SKIP: 'cp36* cp37* cp38* *musllinux*'

and then wondered whether I could use the commit version that adds support for manyline_2_34, i.e.

- name: Build Python wheels
  uses: pypa/cibuildwheel@9c75ea15c2f31a77e6043b80b1b7081372319d85
  env:
    CIBW_ARCHS: auto64
    CIBW_BUILD: 'cp*'
    CIBW_ENVIRONMENT_MACOS: MACOSX_DEPLOYMENT_TARGET=13.0
    CIBW_MANYLINUX_X86_64_IMAGE: manylinux_2_34
    CIBW_SKIP: 'cp36* cp37* cp38* *musllinux*'

and... sure enough, it's all working fine for me now. 🥳

[joerick]

ah yeah, I think we had intended to get a patch release out with manylinux_2_34 before moving on to working on v3.0. That could still be backported to a v2.x branch if there's a lot of demand.

[agarny]

It would be nice to have an official v2.x version not least since now ubuntu-latest on GitHub Actions is Ubuntu 24.04, but... at the same time one can still use the manulinux_2_34 commit, if needed. So, personally, I am fine.

[henryiii]

FYI, manulinux_2_34 is very modern (meaning anyone using your package must be on a recent Linux distro) and most packages are using 2014 still. There are possibly cases to use it, but I think most packages will not need to use it within the next month or two. I did want try to ship it in a patch release, but Joe wanted it to be a feature of 3.0. I don’t think 3.0 is that far away, so this is probably a fine solution special cases for now. Does someone really needs it in a patch release, or we need to make a patch release for another reason, I would be fine to include it.

[agarny]

My package is targeted at Ubuntu 22.04 and later, but I understand and agree with what you are saying.

[mayeut]

There's no need to wait for the commit to land in a release or use a specific commit to use a specific image, you can use already existing options in v2.x:
e.g. CIBW_MANYLINUX_X86_64_IMAGE=quay.io/pypa/manylinux_2_34_x86_64:2025.01.18-1

Please make sure you understand the caveats revealed by pypa/manylinux#1725 that were discovered after the commit in cibuildwheel (so the docs need to be updated here).

Given manylinux_2_34 & manylinux_2_28 are using the same gcc toolchain, my recommendation would be not to use manylinux_2_34 unless you have some dependencies you can't rebuild that can't be used on manylinux_2_28.

[agarny]

There's no need to wait for the commit to land in a release or use a specific commit to use a specific image, you can use already existing options in v2.x: e.g. CIBW_MANYLINUX_X86_64_IMAGE=quay.io/pypa/manylinux_2_34_x86_64:2025.01.18-1

Yes, I was reminded of that earlier today when checking the doc.

Please make sure you understand the caveats revealed by pypa/manylinux#1725 that were discovered after the commit in cibuildwheel (so the docs need to be updated here).

Hmm, I was not aware of this somewhat big caveat!

Given manylinux_2_34 & manylinux_2_28 are using the same gcc toolchain, my recommendation would be not to use manylinux_2_34 unless you have some dependencies you can't rebuild that can't be used on manylinux_2_28.

Well, my library and all the third-party libraries it relies on are built on Ubuntu 22.04, which means that when I try to build my Python wheels using manylinux_2_28 I get tons of undefined references for __libc_single_threaded and the like. From what I understand, those have been removed in glibc 2.31, hence I want/wanted to switch to manylinux_2_34.

Technically, I could build everything (incl. the third-party libraries) on Ubuntu 20.04 (and thus use manylinux_2_28), but I use GitHub Actions for this and they just made ubuntu-latest point to unbutu-24.04, so I was hoping to target Ubuntu 22.04 and later.

[agarny]

FWIW, I have just tested my Python wheels generated using manylinux_2_34 and they work fine for me on both Ubuntu 22.04 and later, which is what I am targeting.