#68606 closed defect (wontfix)
smlnj: update to the new version, retain current as smlnj-legacy (following upstream)
| Reported by: | barracuda156 | Owned by: | tobypeterson |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.8.1 |
| Keywords: | arm64 | Cc: | tobypeterson |
| Port: | hamlet, smlnj |
Description (last modified by barracuda156)
Dependencies are broken on arm64, since smlnj (legacy) does not support it: https://ports.macports.org/port/hamlet/details
(Current smlnj is 64-bit-only, so we will need to retain a legacy version.)
- S. I can maintain the legacy version, if the current port maintainer will not have interest in that.
Change History (16)
comment:1 follow-up: 2 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | tobypeterson added |
|---|---|
| Keywords: | bigsur monterey sonoma removed |
| Port: | smlnj added |
comment:2 Changed 6 months ago by barracuda156
Replying to ryandesign:
Error: Cannot install hamlet for the arch 'arm64' because Error: its dependency smlnj only supports the archs 'x86_64 i386 ppc'.
Ah, fair enough, I should have looked into the log. Sorry about that.
Current smlnj is what is smlnj-legacy with upstream: it is still maintained but perhaps without new platforms added. New smlnj is only 64-bit: https://github.com/smlnj/smlnj/issues/274
(So whenever we upgrade, a legacy version should be retained for ppc and i386.)
comment:3 Changed 6 months ago by barracuda156
| Description: | modified (diff) |
|---|---|
| Summary: | hamlet does not build for aarch64 → smlnj: update to the new version, retain current as smlnj-legacy (following upstream) |
comment:4 Changed 6 months ago by barracuda156
| Owner: | changed from barracuda156 to tobypeterson |
|---|
comment:5 Changed 6 months ago by barracuda156
| Description: | modified (diff) |
|---|
comment:6 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
I don't recommend creating ports whose names include the ambiguous word "legacy". If a port is needed for an older version, just use the version or branch in the port name.
comment:7 follow-up: 8 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
Except, I suppose, if upstream maintains a separate development line by that name.
comment:8 Changed 6 months ago by barracuda156
Replying to ryandesign:
Except, I suppose, if upstream maintains a separate development line by that name.
Yes, this is what I referred; here it is upstream-chosen (I submitted a patch for PowerPC there earlier, so knew the repo).
comment:9 Changed 6 months ago by tobypeterson
Current smlnj is 64-bit-only, so we will need to retain a legacy version.
What is current smlnj? The version we have (110.99.3), and the current version (110.99.4) still appear to support the same architectures as always (x86_64, ppc, i386, sparc).
comment:10 follow-up: 11 Changed 6 months ago by tobypeterson
Are you referring to the experimental releases that have the year in their version? Those don't seem anywhere near ready; I can't imagine we'd make a port for that until it supports arm64, at the very least...
comment:11 Changed 6 months ago by barracuda156
Replying to tobypeterson:
Are you referring to the experimental releases that have the year in their version? Those don't seem anywhere near ready; I can't imagine we'd make a port for that until it supports arm64, at the very least...
Indeed, they say only Intel is known to work. Oh wow.
I guess, I should just see if I can build hamlet with mlton instead, which builds fine for all archs (strictly speaking, aside of ppc64, but it is broken in Macports anyway).
comment:12 Changed 6 months ago by tobypeterson
Sure, give that a shot. Looks like hamlet will support several SML backends. Who knows when smlnj will support aarch64...
comment:13 Changed 6 months ago by tobypeterson
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
comment:14 follow-up: 16 Changed 6 months ago by tobypeterson
That said, if you want to a submit an update to 110.99.4, that'd be helpful. It won't build on Apple silicon machines, and I don't have immediate access to an intel machine.
comment:15 Changed 6 months ago by tobypeterson
Or we can just wait for upstream to figure everything out... arm64 support will arrive some day, one imagines...
comment:16 Changed 6 months ago by barracuda156
Replying to tobypeterson:
That said, if you want to a submit an update to 110.99.4, that'd be helpful. It won't build on Apple silicon machines, and I don't have immediate access to an intel machine.
I think I can do that in some days. Won’t hurt, and perhaps we can drop our patch, since upstream merged it, I believe.
I thought to use smlnj to bootstrap mlton for ppc64 in fact, as they do not have binaries for that arch, but this is not in immediate plans, since both Macports setup and my own setup on Leopard are broken for ppc64 at the moment.