Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1271234
| Summary: | [epel7s390x] uwsgi SRPM does not build correctly on s390x | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | IBM Bug Proxy <bugproxy> | ||||
| Component: | uwsgi | Assignee: | Jorge Gallegos <kad> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | epel7 | CC: | dan, dhorak, hannsj_uhl, jkachuck, kad | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | s390x | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-04-14 11:08:24 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1267648 | ||||||
| Attachments: |
|
||||||
|
Description
IBM Bug Proxy
2015-10-13 12:51:49 UTC
The EPEL 7 SRPM for uwsgi-2.0.11.1-1 https://dl.fedoraproject.org/pub/epel/7/SRPMS/u/uwsgi-2.0.11.1-1.el7.src.rpm does not build correctly in Mock on s390x. The build message is copied below, jvm cannot be found by the build: ############## end of uWSGI configuration ############# total build time: 25 seconds *** uWSGI is ready, launch it with ./uwsgi *** + CFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -march=z196 -mtune=zEC12 -Wno-unused-but-set-variable' + python uwsgiconfig.py --plugin plugins/systemd_logger fedora using profile: buildconf/fedora.ini detected include path: ['/usr/lib/gcc/s390x-redhat-linux/4.8.3/include', '/usr/local/include', '/usr/include'] *** uWSGI building and linking plugin plugins/systemd_logger *** [gcc -pthread] systemd_logger_plugin.so build time: 0 seconds *** systemd_logger plugin built and available in systemd_logger_plugin.so *** + CFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -march=z196 -mtune=zEC12 -Wno-unused-but-set-variable' + python uwsgiconfig.py --plugin plugins/jvm fedora /usr/bin/ld: cannot find -ljvm collect2: error: ld returned 1 exit status using profile: buildconf/fedora.ini detected include path: ['/usr/lib/gcc/s390x-redhat-linux/4.8.3/include', '/usr/local/include', '/usr/include'] *** uWSGI building and linking plugin plugins/jvm *** [gcc -pthread] jvm_plugin.so *** unable to build jvm plugin *** ins/jvm *** [gcc -pthread] jvm_plugin.so *** unable to build jvm plugin *** Created attachment 1082408 [details]
uwsgi-build-log
Would love if you could provide me with the mock config you're using, I don't have an epel7 config here. ------- Comment From hannsj_uhl.com 2016-03-29 11:55 EDT------- Comment from Bryan Chan 2016-03-29 11:35:39 EDT Sorry for the delay. Our mock config was a home-made config based on the EPEL 7 mock config for x86, however all the repos were replaced with internal ones that we had to populate manually by rebuilding all EPEL 7 SRPMs. This is because s390x is not yet a supported EPEL architecture. I think the problem is reproducible with rpmbuild, outside the mock. So a mock config for s390x shouldn't be a prerequisite for fixing the issue. ------- Comment From urjawere.com 2017-03-20 02:28 EDT------- Any Updates? This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component. This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component. With no real activity in this bug for years, I'm now closing this on the IBM side. If the problem still needs to be addressed, please re-open or preferably open a new bug. Thanks. |