#53892 closed defect (fixed)
sbcl @1.3.16: build failure
Reported by: | dyne2meter | Owned by: | easieste@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | mavericks | Cc: | |
Port: | sbcl |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Extract from log:
:info:build Welcome to LDB, a low-level debugger for the Lisp runtime environment. :info:build ldb> :info:build Command failed: ulimit -s 8192 && unset LD_PREBIND && unset LD_PREBIND_ALLOW_OVERLAP && export SBCL_MACOSX_VERSION_MIN=10.5 && cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_sbcl/sbcl/work/sbcl-1.3.16 && export CC && CC=/usr/bin/clang && export CXX && CXX=/usr/bin/clang++ && export CPP && CPP==/usr/bin/cpp && sh ./make.sh --fancy --prefix=/opt/local --xc-host="/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_sbcl/sbcl/work/sbcl-1.0.55-x86-darwin/src/runtime/sbcl --core /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_sbcl/sbcl/work/sbcl-1.0.55-x86-darwin/output/sbcl.core --disable-debugger --sysinit /dev/null --userinit /dev/null" :info:build Exit code: 128 :error:build Failed to build sbcl: command execution failed :debug:build Error code: NONE :debug:build Backtrace: command execution failed :debug:build while executing :debug:build "$procedure $targetname"
Attachments (2)
Change History (13)
comment:1 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | easieste@… removed |
---|---|
Description: | modified (diff) |
Keywords: | mavericks added; ldb (lisp debugger) removed |
Owner: | set to easieste@… |
Port: | 1.3.16 removed |
Status: | new → assigned |
Summary: | sbcl 1.3.16 build failure - Mavericks → sbcl @1.3.16: build failure |
comment:2 Changed 8 years ago by dyne2meter
Also: this warning is issued right after the build phase commences:
Warning: reinplace s|CC=gcc|CC=/usr/bin/clang| didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_sbcl/sbcl/work/sbcl-1.3.16/contrib/asdf-module.mk
comment:3 Changed 8 years ago by easye
Unfortunately, I do not have access to a macOS 10.9 Mavericks instance to help debug/test, so there is not much I can do at the moment to address this failure.
Were someone using Mavericks able to get me patches to address the problem, I would be happy to shepherd those patches to commit status.
comment:4 follow-up: 5 Changed 8 years ago by dyne2meter
Oh, don't worry about that. It fails in the same way in El Capitan.
comment:5 Changed 8 years ago by easye
Replying to dyne2meter:
Oh, don't worry about that. It fails in the same way in El Capitan.
Hmm. I don't have El Capitan either (just two Sierra machines).
Any known failures on macOS 10.12 (Sierra)?
comment:6 Changed 8 years ago by dyne2meter
This business with sbcl is not a deal breaker for me. I need it for building maxima, but there are just-about-up-to-the-moment pre-built packages available elsewhere.
MacPorts is kind of a canary-in-the-coal-mine for me and my systems. My machines date from 2008 and won't even download Sierra. I have maxima, which depends on sbcl, but can get an up-to-date built package elsewhere. Most of my interest in MacPorts is for my python installation, but there are other ways to go for that, as well.
A few months back, sbcl was again broken for me, and it took a very long time before it was patched; I was not in on the process.
To help out here, should I download a source package for sbcl to see if I can build it outside the MacPorts system?
comment:7 follow-up: 8 Changed 8 years ago by dyne2meter
The actual glitch is at least also reported here, trying to build 1.3.16 with existing 1.2.11:
https://bugs.launchpad.net/sbcl/+bug/1678347
The error message appears just before the build process goes into the lisp debugger:
fatal error encountered in SBCL pid 6572: no size function for object at 0x21cb0050 (widetag 0x31)
I don't understand the rest of the exchange at launchpad, dated April 1.
comment:8 Changed 8 years ago by easye
Replying to dyne2meter:
The actual glitch is at least also reported here, trying to build 1.3.16 with existing 1.2.11:
That looks like enough information for me to get a patch out for y'all to test.
I'm attending the 2017 European Lisp Symposium at the moment, so getting concentrated time to work through this is a bit tough, but I should be able to get something testable done tomorrow.
Thanks for the research!
comment:10 Changed 8 years ago by easye
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
This should work now with <https://github.com/macports/macports-ports/commit/69e65bfee913bab79ab474a1c90d3ab3cb0f27b5> if the problem is indeed present on non-AVX capable macOS instances.
Please let me know if this doesn't work.
comment:11 Changed 8 years ago by dyne2meter
This works on both Mavericks and El Cap. Thanks so much for the patch. Glad I could help, even a little. Now I even know the first thing about about AVX. Cheers.
Please attach the main.log file.