Bug 2358214 - chez-scheme excludearch on s390x
Summary: chez-scheme excludearch on s390x
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: chez-scheme
Version: rawhide
Hardware: s390x
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F-ExcludeArch-s390x 2353163
TreeView+ depends on / blocked
 
Reported: 2025-04-08 08:45 UTC by Jonny Heggheim
Modified: 2025-04-23 00:52 UTC (History)
2 users (show)

Fixed In Version: chez-scheme-10.1.0-4.fc41 chez-scheme-10.1.0-4.fc42 chez-scheme-10.1.0-4.fc40 chez-scheme-10.1.0-4.el9
Clone Of:
Environment:
Last Closed: 2025-04-20 00:26:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-1576 0 None None None 2025-04-10 04:53:28 UTC

Description Jonny Heggheim 2025-04-08 08:45:03 UTC
chez-scheme.spec:
> # 10.0 fails with "illegal pb instruction"
> ExcludeArch:    s390x

https://docs.fedoraproject.org/en-US/packaging-guidelines/#_architecture_build_failures

Reproducible: Always

Comment 1 Jonny Heggheim 2025-04-08 08:47:47 UTC
Koji build: https://koji.fedoraproject.org/koji/taskinfo?taskID=131271295

Seem to compile on s390x.

Comment 2 Jonny Heggheim 2025-04-08 09:08:42 UTC
Seems like Debian have patches for 10.0.0 for s390x https://sources.debian.org/src/chezscheme/10.0.0%2Bdfsg-5/debian/patches/ 

Have it been reported upstream?

Have it been fixed in 10.1.0?

Comment 3 Jonny Heggheim 2025-04-08 09:13:01 UTC
The release notes [1] for 10.1.0 includes fixes for s390x:

> 3.4. Bytecode endianness handling on s390x, m68k, and hppa (10.1.0)
> The bytecode endianness on s390x, m68k, and hppa architectures has been fixed.

[1] https://cisco.github.io/ChezScheme/release_notes/v10.1.0/release_notes.html

Comment 4 Jens Petersen 2025-04-10 04:52:46 UTC
Thanks for this - I will look more into it, need a little time.

Happy to accept help, like a PR too.

One problem anyway is that the pseudo-bytecode is very slow.
Though I think racket might be even slower (or was it the other way around)?

Comment 5 Jens Petersen 2025-04-10 07:10:28 UTC
You are right, 10.1 seems to build fine

Comment 6 Fedora Update System 2025-04-10 11:08:42 UTC
FEDORA-2025-101416753b (chez-scheme-10.1.0-4.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-101416753b

Comment 7 Fedora Update System 2025-04-10 12:13:41 UTC
FEDORA-2025-df591ee1bc (chez-scheme-10.1.0-4.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-df591ee1bc

Comment 8 Jonny Heggheim 2025-04-10 12:37:30 UTC
I started building of schemesh, that package contains 570 tests, so bugs on s390x should be found quickly.


https://koji.fedoraproject.org/koji/taskinfo?taskID=131372104

Comment 9 Fedora Update System 2025-04-11 02:11:39 UTC
FEDORA-2025-101416753b has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-101416753b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-101416753b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2025-04-11 02:29:34 UTC
FEDORA-2025-df591ee1bc has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-df591ee1bc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-df591ee1bc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2025-04-11 02:47:59 UTC
FEDORA-2025-deb7ec3e79 (chez-scheme-10.1.0-4.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-deb7ec3e79

Comment 12 Fedora Update System 2025-04-11 04:17:11 UTC
FEDORA-EPEL-2025-a6ec2b589d (chez-scheme-10.1.0-4.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a6ec2b589d

Comment 13 Fedora Update System 2025-04-13 03:17:21 UTC
FEDORA-2025-deb7ec3e79 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-deb7ec3e79`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-deb7ec3e79

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2025-04-15 16:52:24 UTC
FEDORA-EPEL-2025-a6ec2b589d has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-a6ec2b589d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 15 Fedora Update System 2025-04-20 00:26:37 UTC
FEDORA-2025-df591ee1bc (chez-scheme-10.1.0-4.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2025-04-20 04:22:20 UTC
FEDORA-2025-101416753b (chez-scheme-10.1.0-4.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2025-04-21 01:40:19 UTC
FEDORA-2025-deb7ec3e79 (chez-scheme-10.1.0-4.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 18 Fedora Update System 2025-04-23 00:52:41 UTC
FEDORA-EPEL-2025-a6ec2b589d (chez-scheme-10.1.0-4.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.