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

Crossbuilding fails #25

Open
waja opened this issue May 16, 2023 · 1 comment
Open

Crossbuilding fails #25

waja opened this issue May 16, 2023 · 1 comment

Comments

@waja
Copy link

waja commented May 16, 2023

Hi,

I tried to crossbuild for aarch64 on x86_64:

docker run --rm --privileged=true --volume=".:/rpmbuild" -w "/rpmbuild" \
 --volume="/output:/rpmbuild/output" -e MOUNT_POINT="/rpmbuild" \
 -e MOCK_CONFIG=fedora-rawhide-aarch64 -e SOURCES="monitoring-plugins-b784428.tar.gz" \
 -e SPEC_FILE=monitoring-plugins-git.spec  -e NETWORK="true" -e NO_CLEANUP="true" \
 ghcr.io/waja/mock-rpmbuilder:latest

https://github.com/waja/docker-mock-rpmbuilder is just a fork, but with CI pipelines to generate and upload images to GHCR.

There are several error: failed to exec scriptlet interpreter /bin/sh: Exec format error errors and finally the build fails with Error: call to /usr/sbin/ldconfig failed.nError: call to /usr/sbin/iconvconfig failed.nError: call to /usr/sbin/ldconfig failed.n.

The full output can be found in the mock-builder.log.

Thanks Jan

@k0ste
Copy link
Contributor

k0ste commented May 17, 2023

In your log:

  Running scriptlet: elfutils-default-yama-scope-0.189-2.fc39.noarch     76/140
error: failed to exec scriptlet interpreter /bin/sh: Exec format error
warning: %post(elfutils-default-yama-scope-0.189-2.fc39.noarch) scriptlet failed, exit status 127

Error in POSTIN scriptlet in rpm package elfutils-default-yama-scope
  Running scriptlet: p11-kit-trust-0.24.1-6.fc38.aarch64                 79/140
error: failed to exec scriptlet interpreter /bin/sh: Exec format error
warning: %post(p11-kit-trust-0.24.1-6.fc38.aarch64) scriptlet failed, exit status 127

Error in POSTIN scriptlet in rpm package p11-kit-trust
  Running scriptlet: ca-certificates-2023.2.60-2.fc38.noarch             99/140
error: failed to exec scriptlet interpreter /bin/sh: Exec format error
error: %prein(ca-certificates-2023.2.60-2.fc38.noarch) scriptlet failed, exit status 127

Error in PREIN scriptlet in rpm package ca-certificates
  Installing       : rpm-sequoia-1.4.0-2.fc39.aarch64                   100/140
error: ca-certificates-2023.2.60-2.fc38.noarch: install failed
  Running scriptlet: tpm2-tss-4.0.1-3.fc38.aarch64                      132/140
error: failed to exec scriptlet interpreter /bin/sh: Exec format error
error: %prein(tpm2-tss-4.0.1-3.fc38.aarch64) scriptlet failed, exit status 127

Error in PREIN scriptlet in rpm package tpm2-tss
  Installing       : ima-evm-utils-1.4-7.fc38.aarch64                   133/140
error: tpm2-tss-4.0.1-3.fc38.aarch64: install failed
  Running scriptlet: dnf-4.15.0-1.fc39.noarch                           139/140
error: failed to exec scriptlet interpreter /bin/sh: Exec format error
warning: %post(dnf-4.15.0-1.fc39.noarch) scriptlet failed, exit status 127

Error in POSTIN scriptlet in rpm package dnf
  Running scriptlet: rpm-4.18.1-3.fc39.aarch64                          140/140
error: failed to exec scriptlet interpreter /bin/sh: Exec format error
error: %prein(rpm-4.18.1-3.fc39.aarch64) scriptlet failed, exit status 127

Error in PREIN scriptlet in rpm package rpm
  Running scriptlet: filesystem-3.18-4.fc39.aarch64                     140/140
error: rpm-4.18.1-3.fc39.aarch64: install failed

  Running scriptlet: rpm-4.18.1-3.fc39.aarch64                          140/140
error: failed to exec scriptlet interpreter /bin/sh: Exec format error
warning: %transfiletriggerin(glib2-2.76.2-1.fc39.aarch64) scriptlet failed, exit status 127

Error in <unknown> scriptlet in rpm package rpm

Overall

Failed:
  ca-certificates-2023.2.60-2.fc38.noarch       rpm-4.18.1-3.fc39.aarch64
  tpm2-tss-4.0.1-3.fc38.aarch64                Error: Transaction failed

You should investigate what exactly happened with this packages

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

2 participants