[MacPorts] #65188: sbcl: fatal error encountered in SBCL pid 16153: dynamic space too small for core
MacPorts
noreply at macports.org
Wed May 18 15:10:31 UTC 2022
#65188: sbcl: fatal error encountered in SBCL pid 16153: dynamic space too small
for core
---------------------------+----------------------
Reporter: barracuda156 | Owner: easye
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.7.2
Resolution: | Keywords:
Port: sbcl |
---------------------------+----------------------
Comment (by barracuda156):
Replying to [comment:10 easye]:
> Replying to [comment:9 easye]:
> > Support for Darwin/PPC was removed with sbcl-2.2.3
<http://sbcl.org/news.html>.
>
> A statement from the SBCL maintainer via IRC:
>
> {{{
> <Krystof> easye: I think it's worth saying that if there are users
willing to
> step up and maintain our ppc/darwin support, we'd reinstate it
on
> that basis
[13:20]
> <Krystof> the problem we were having is: no hardware, no access to
hardware,
> no demand from users, no ability to check whether changes for
other
> platforms cause breakage
[13:21]
> }}}
If the issue is purely technical, then it is not too hard to build PPC
code on a modern Intel Mac. Set up 10.6.x in VM, make sure to install
Rosetta, build Macports for PPC natively, run PPC binaries. I have such
set up on my MacMini at home with Catalina.
But of course, the problem may rather be economical: upstream has limited
time and may prefer use it for smth else. This is understandable, so my
questions here do not imply I expect others to fix the thing and keep
maintaining. It just might happen that for someone from developers errors
I reported are known and trivial, while for me it may take days or weeks.
My general understanding (which can be wrong) is that compilers, if
properly designed, are cross-platform, and we don’t need to change PPC
assembler, it just has to be fixed once. If gcc11 builds, sbcl should ))
P. S. I don’t want to create a burden for anyone, and lack of hardware or
spare time is perfectly understandable. If someone comes up with a useful
suggestion, great, otherwise I will try to fix it myself and update on
success or failure.
I will look into assembler error, it’s two lines of code after all, should
be fixable.
--
Ticket URL: <https://trac.macports.org/ticket/65188#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list