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

build-unit-test-docker.sh: ppc64le: Latest Ubuntu Noble release fails to build - Cannot change mode to rwxr-xr-x: Operation not permitted #35

Open
geissonator opened this issue Feb 26, 2024 · 0 comments

Comments

@geissonator
Copy link
Contributor

Not sure what's going on yet but the latest Ubuntu Noble release is not working with our ppc64le boxes. While building the container, it spews out errors like this (there are 100's of them, seems to be every directory in the tar file):

boost: tar: boost-1.84.0/libs/thread/test/experimental/parallel/v1: Cannot change mode to rwxr-xr-x: Operation not permitted
boost: tar: boost-1.84.0/libs/thread/test/experimental/parallel/v2: Cannot change mode to rwxr-xr-x: Operation not permitted
boost: tar: boost-1.84.0/libs/thread/test/experimental/parallel: Cannot change mode to rwxr-xr-x: Operation not permitted
boost: tar: boost-1.84.0/libs/thread/test/experimental: Cannot change mode to rwxr-xr-x: Operation not permitted
boost: tar: boost-1.84.0/libs/thread/test/sync/futures/when_all: Cannot change mode to rwxr-xr-x: Operation not permitted
boost: tar: boost-1.84.0/libs/thread/test/sync/futures/future: Cannot change mode to rwxr-xr-x: Operation not permitted

It's not just boost, it seems to be all of the tar files we try to download and install.

I manually started up a container and ran the following and hit the error as well:

curl -L https://github.com/boostorg/boost/releases/download/boost-1.84.0/boost-1.84.0.tar.gz | tar -xzv && cd boost* && ./bootstrap.sh --prefix=/usr/local --with-libraries=context,coroutine,url && ./b2 && ./b2 install --prefix=/usr/local

I tried a variety of different options to tar in regards to permission but none of them helped. I verified the same test works fine with the previous Ubuntu release (mantic) on the same machine. This also works fine on our x86 system.

If I manually try to change the dir permissions using chmod, it works fine after the fact (we're running as root in the container so the permission errors really don't make much sense to me).

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

1 participant