FTBFS on arm64 due to LTO

Bug #2006524 reported by Sergio Durigan Junior
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sbcl (Debian)
New
Unknown
sbcl (Ubuntu)
Fix Released
Critical
Sergio Durigan Junior

Bug Description

sbcl is currently FTBFSing on arm64 due to LTO:

/usr/bin/ld: /tmp/cc1VPXKi.ltrans1.ltrans.o: in function `interrupt_handle_now':
/<<PKGBUILDDIR>>/src/runtime/funcall.c:72: undefined reference to `call_into_lisp'
/usr/bin/ld: /tmp/cc1VPXKi.ltrans1.ltrans.o: in function `interrupt_handle_now_handler':
/<<PKGBUILDDIR>>/src/runtime/funcall.c:72: undefined reference to `call_into_lisp'
/usr/bin/ld: /tmp/cc1VPXKi.ltrans1.ltrans.o: in function `maybe_gc':
/<<PKGBUILDDIR>>/src/runtime/funcall.c:53: undefined reference to `call_into_lisp'
/usr/bin/ld: /<<PKGBUILDDIR>>/src/runtime/funcall.c:46: undefined reference to `call_into_lisp'
/usr/bin/ld: /tmp/cc1VPXKi.ltrans1.ltrans.o: in function `lisp_memory_fault_error':
/<<PKGBUILDDIR>>/src/runtime/funcall.c:62: undefined reference to `call_into_lisp'
/usr/bin/ld: /tmp/cc1VPXKi.ltrans1.ltrans.o:/<<PKGBUILDDIR>>/src/runtime/funcall.c:62: more undefined references to `call_into_lisp' follow
/usr/bin/ld: /tmp/cc1VPXKi.ltrans3.ltrans.o: in function `gc_heap_exhausted_error_or_lose':
/<<PKGBUILDDIR>>/src/runtime/gencgc.c:1447: undefined reference to `do_pending_interrupt'
collect2: error: ld returned 1 exit status
make[2]: *** [GNUmakefile:102: sbcl] Error 1

https://launchpadlibrarian.net/650311569/buildlog_ubuntu-lunar-arm64.sbcl_2%3A2.2.9-1_BUILDING.txt.gz

Changed in sbcl (Debian):
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sbcl - 2:2.2.9-1ubuntu2

---------------
sbcl (2:2.2.9-1ubuntu2) lunar; urgency=medium

  * d/rules: Fix typo in the last upload.

 -- Sergio Durigan Junior <email address hidden> Tue, 07 Feb 2023 19:54:20 -0500

Changed in sbcl (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.