Opened 2 years ago
Last modified 23 months ago
#2441 accepted defect
pkg-oss - build error
Reported by: | Alexander Kubyshkin | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | nginx-package | Version: | |
Keywords: | pkg-oss, docker | Cc: | |
uname -a: | docker, rockylinux:8 | ||
nginx -V: | any |
Description
Hi guys,
Trying to build a module for nginx, but build error arises:
===> Building nginx-module-rtmp package Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.dK9eXn + umask 022 + cd /root/rpmbuild/BUILD + cd /root/rpmbuild/BUILD + rm -rf nginx-plus-module-rtmp-1.17.6 + /usr/bin/mkdir -p nginx-plus-module-rtmp-1.17.6 + cd nginx-plus-module-rtmp-1.17.6 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + tar --strip-components=1 -zxf /root/rpmbuild/SOURCES/nginx-1.17.6.tar.gz tar (child): /root/rpmbuild/SOURCES/nginx-1.17.6.tar.gz: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now error: Bad exit status from /var/tmp/rpm-tmp.dK9eXn (%prep) Bad exit status from /var/tmp/rpm-tmp.dK9eXn (%prep)
How to reproduce:
docker run --rm rockylinux:8 bash -c 'yum install -y wget && wget https://hg.nginx.org/pkg-oss/raw-file/default/build_module.sh && bash build_module.sh -y -r 20 https://github.com/arut/nginx-rtmp-module.git'
Same error on different platforms - aarch64 and amd64.
Full output is attached(aarch64).
Attachments (1)
Change History (2)
by , 2 years ago
Attachment: | docker-run-output.txt added |
---|
comment:1 by , 23 months ago
Component: | documentation → nginx-package |
---|---|
Priority: | major → minor |
Status: | new → accepted |
build_module.sh from tip does not support older builder system as used in R20. For R20, please use https://hg.nginx.org/pkg-oss/file/target-plus-r20/build_module.sh ( build_module.sh from R20 branch).
Some discussion around it can be found on https://mailman.nginx.org/pipermail/nginx-ru/2023-January/4KNTIHSFQHXPOHPSMPU46HMDBKMWBLCZ.html (and later mails on this thread).
This can be fixed, but it's definitely not a high priority at this moment.
Docker run full output