Closed sfyatee closed 1 year ago
Demian Garcia writes:
bin/acme: exec devdraw: No such file or directory acme: can't open display: muxrpc: unexpected eof
A bit more info about your setup would help. How recent is your plan9port build? What version of MacOS? Hardware model?
I just did a pull and rebuilt and it's working fine for me.
Darwin hqmac49.local 22.3.0 Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000 arm64 2021 MacBook Pro w/M1 Pro CPU
--lyndon
System Version: macOS 13.2.1 (22D68)
Kernel Version: Darwin 22.3.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Chip: Apple M1 Pro
Total Number of Cores: 8 (6 performance and 2 efficiency)
Memory: 16 GB
System Firmware Version: 8419.80.7
OS Loader Version: 8419.80.7
System Version: macOS 13.2.1 (22D68) Kernel Version: Darwin 22.3.0 Boot Volume: Macintosh HD Boot Mode: Normal Chip: Apple M1 Pro Total Number of Cores: 8 (6 performance and 2 efficiency) Memory: 16 GB System Firmware Version: 8419.80.7 OS Loader Version: 8419.80.7
The non-GUI elements build fine, only when I try to launch gui-plan9 applications is when it begins to fail on me. I'm not sure where to start looking, either something is corrupted on my system of I'm missing a piece of software. The plan9port I try to build is the most recent one here on Github.
FWIW, I'm seeing the same issue when trying to package for Guix (similar to Nix). Building e2a141ae. I suspect it's just a local issue, however, since building much older commits results in the same error.
If you're willing to run Guix, then the following should be reproduction steps:
Build and run
$ "$(guix build --file=plan9.scm plan9port)/bin/9" acme
@9arcia Why did you close this issue? If you discovered the underlying cause, please share.
@xelxebar apologies I forgot to follow up. it was simple user error. I simply had to put it in my path correctly. I am using the fish shell, and was unfamiliar on how it was done correctly.
@9arcia Thanks.
Hrm. Arguably, sam
and acme
shouldn't be relying on PATH
and instead look directly under 9PATH/bin
. Maybe this is a path fixup issue during the install process?
I am not sure if it was a recent macOS update that broke plan9port, but now I get this message:
If I recall correctly it was working well a few months ago. I'm not sure when was the last time I tried plan9port.