Opened 12 months ago
Closed 4 months ago
#72727 closed request (fixed)
New port request: Unicon
| Reported by: | kwolcott | Owned by: | commitmaniac <201806046+commitmaniac@…> |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | unicon |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Please consider creating a port for the Unicon language.
https://unicon.sourceforge.io/downloads.html
https://github.com/uniconproject/unicon
It seems to build ok with:
CC=clang CXX=clang++ ./configure --prefix=/opt/unicon make sudo make install
But all binaries installed under /opt/unicon/bin are killed immediately by zsh (why?)<<<<<<<<<<<<
Example:
/opt/unicon/bin/iconc -v zsh: killed /opt/unicon/bin/iconc -v file /opt/unicon/bin/iconc /opt/unicon/bin/iconc: Mach-O 64-bit arm64 executable, flags:<NOUNDEFS|DYLDLINK|TWOLEVEL|PIE> unicon: file /opt/unicon/bin/icont /opt/unicon/bin/icont: Mach-O 64-bit arm64 executable, flags:<NOUNDEFS|DYLDLINK|TWOLEVEL|PIE>
Attachments (2)
Change History (6)
comment:1 Changed 12 months ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|---|
| Port: | unicon added |
Changed 12 months ago by kwolcott
| Attachment: | iconc-2025-07-25-211858.ips.bz2 added |
|---|
Changed 12 months ago by kwolcott
| Attachment: | icont-2025-07-25-210844.ips.bz2 added |
|---|
comment:2 Changed 12 months ago by ryandesign (Ryan Carsten Schmidt)
I see the backtrace is entirely within dyld; no application code is involved.
I see the message:
Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
Does running sudo /usr/sbin/purge (or just waiting awhile) fix it? (See #72689 where that fixed another instance of this type of crash.)
comment:4 Changed 4 months ago by commitmaniac <201806046+commitmaniac@…>
| Owner: | set to commitmaniac <201806046+commitmaniac@…> |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
A crash log might have been created in ~/Library/Logs/DiagnosticReports; if so, that hopefully explains why the program couldn't be launched. If the reason is not apparent, you could attach the crash log here and we'll have a look.