Bug 2226390 - [ppc64le] racket fails to build
Summary: [ppc64le] racket fails to build
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: racket
Version: 40
Hardware: ppc64le
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-25 20:02 UTC by Fedora Release Engineering
Modified: 2024-05-21 01:17 UTC (History)
2 users (show)

Fixed In Version: racket-8.12-2.fc41 racket-8.12-2.fc40
Clone Of:
Environment:
Last Closed: 2024-05-21 01:17:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2023-07-25 20:02 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2023-07-25 20:02 UTC, Fedora Release Engineering
no flags Details
state.log (1003 bytes, text/plain)
2023-07-25 20:02 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2023-07-25 20:02:11 UTC
racket failed to build from source in Fedora rawhide/f39

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
Please fix racket at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
racket will be orphaned. Before branching of Fedora 40,
racket will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Fedora Release Engineering 2023-07-25 20:02:20 UTC
Created attachment 1979552 [details]
build.log

file build.log too big, will only attach last 32768 bytes

Comment 2 Fedora Release Engineering 2023-07-25 20:02:24 UTC
Created attachment 1979553 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2023-07-25 20:02:26 UTC
Created attachment 1979554 [details]
state.log

Comment 4 Jens Petersen 2023-07-26 06:41:33 UTC
I think an simple and acceptable workaround for now would be to add `ExcludeArch: ppc64le`

(Actually I wanted to update my copr anyway, but the builds are tainted with the buildroot path :-/)

Comment 5 Miro Hrončok 2023-08-01 22:39:13 UTC
Automation has figured out the package is retired in rawhide.

If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement

Comment 6 Fedora Update System 2023-08-28 03:41:10 UTC
FEDORA-2023-b90f48842f has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b90f48842f

Comment 7 Fedora Update System 2023-08-29 01:24:47 UTC
FEDORA-2023-b90f48842f has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-b90f48842f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b90f48842f

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

Comment 8 Jens Petersen 2023-08-29 03:58:34 UTC
Build also segfaults with 7.9:

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

raco setup: installing: /builddir/build/BUILDROOT/racket-7.9-1.fc40.ppc64le/usr/share/doc/racket/doc-site.css
raco setup: installing: /builddir/build/BUILDROOT/racket-7.9-1.fc40.ppc64le/usr/share/doc/racket/doc-site.js
raco setup: running: <pkgs>/racket-doc/scribblings/reference/reference.scrbl
make[2]: *** [Makefile:465: install-setup-3m] Aborted (core dumped)
make[2]: Leaving directory '/builddir/build/BUILD/racket-7.9/src/bc'
make[1]: Leaving directory '/builddir/build/BUILD/racket-7.9/src'
make[1]: *** [Makefile:179: install-3m] Error 2
make: Leaving directory '/builddir/build/BUILD/racket-7.9/src'
make: *** [Makefile:110: install] Error 2

Comment 9 Aoife Moloney 2024-02-15 22:56:50 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle.
Changing version to 40.

Comment 10 Jens Petersen 2024-04-29 14:35:02 UTC
Racket 8.12 also fails to build on ppc64le, but I think this is more expected.

Comment 11 Jens Petersen 2024-04-29 14:36:03 UTC
For racket 8.12:

raco setup: making: <pkgs>/drracket/browser/private
raco setup:  in <pkgs>/drracket/browser/private
raco setup: making: <pkgs>/drracket/browser/tests
raco setup:  in <pkgs>/drracket/browser/tests
raco setup: making: <pkgs>/drracket/drracket
raco setup:  in <pkgs>/drracket/drracket
raco setup:  in <pkgs>/drracket/drracket/private
raco setup:  in <pkgs>/images-lib/images/icons
failed
 in build-one
 in loop
 in module->hash
make: *** [Makefile:22: all] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.PmYynb (%build)
    Bad exit status from /var/tmp/rpm-tmp.PmYynb (%build)
RPM build errors:
Child return code was: 1

Comment 12 Jens Petersen 2024-05-02 02:03:27 UTC
Fixed in Rawhide using 8.12 with the portable bytecode backend.

Comment 13 Fedora Update System 2024-05-04 08:20:54 UTC
FEDORA-2024-8273f34848 (racket-8.12-2.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-8273f34848

Comment 14 Fedora Update System 2024-05-05 04:12:53 UTC
FEDORA-2024-8273f34848 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-2024-8273f34848`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-8273f34848

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

Comment 15 Fedora Update System 2024-05-21 01:17:37 UTC
FEDORA-2024-8273f34848 (racket-8.12-2.fc40) has been pushed to the Fedora 40 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.