You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the instructions in the README.md I got two issues:
Readline not found
> brew install sieve-connect
==> Downloading https://ghcr.io/v2/homebrew/core/openssl/3/manifests/3.0.1
######################################################################## 100.0%
==> Downloading https://ghcr.io/v2/homebrew/core/openssl/3/blobs/sha256:331a18b7ac0b35d55adb422268c6b08190b378bdfec915a5f6d0b7
==> Downloading from https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:331a18b7ac0b35d55adb422268c6b08190b378bdf
######################################################################## 100.0%
==> Downloading https://ghcr.io/v2/homebrew/core/Readline/manifests/8.1.2
curl: (22) The requested URL returned error: 404
Error: sieve-connect: Failed to download resource "Readline_bottle_manifest"
Download failed: https://ghcr.io/v2/homebrew/core/Readline/manifests/8.1.2
Error 255
brew install sieve-connect --without-readline
==> Downloading https://ghcr.io/v2/homebrew/core/openssl/3/manifests/3.0.1
Already downloaded: /Users/redacted/Library/Caches/Homebrew/downloads/242b5104bb035508bc4a51aad45a97b19ccf3776c4a2d396d0b5e815bce690d1--openssl@3-3.0.1.bottle_manifest.json
[REDACTED]
==> make install
==> perl Makefile.PL INSTALL_BASE=/usr/local/Cellar/sieve-connect/0.90/libexec
==> make PERL5LIB=/usr/local/Cellar/sieve-connect/0.90/libexec/lib:/usr/local/Cellar/sieve-connect/0.90/libexec/lib/perl5
Last 15 lines from /Users/redacted/Library/Logs/Homebrew/sieve-connect/20.make:
t_werasc (ERASEWORD) found in ltchars
Writing sgtty section of cchars.h... Done.
cc -c -g -pipe -fno-strict-aliasing -fstack-protector-strong -DPERL_USE_SAFE_PUTENV -Os -DVERSION=\"2.38\" -DXS_VERSION=\"2.38\" -iwithsysroot "/System/Library/Perl/5.30/darwin-thread-multi-2level/CORE" ReadKey.c
rm -f blib/arch/auto/Term/ReadKey/ReadKey.bundle
cc -bundle -undefined dynamic_lookup -fstack-protector-strong ReadKey.o -o blib/arch/auto/Term/ReadKey/ReadKey.bundle \
\
chmod 755 blib/arch/auto/Term/ReadKey/ReadKey.bundle
"/usr/bin/perl" "-Iblib/arch" "-Iblib/lib" ReadKey.pm.PL ReadKey.pm
Can't load 'blib/arch/auto/Term/ReadKey/ReadKey.bundle' for module Term::ReadKey: dlopen(blib/arch/auto/Term/ReadKey/ReadKey.bundle, 0x0001): tried: 'blib/arch/auto/Term/ReadKey/ReadKey.bundle' (relative path not allowed in hardened program), '/usr/lib/ReadKey.bundle' (no such file) at /System/Library/Perl/5.30/darwin-thread-multi-2level/DynaLoader.pm line 197.
at /System/Library/Perl/5.30/darwin-thread-multi-2level/DynaLoader.pm line 95.
DynaLoader::croak("Can't load 'blib/arch/auto/Term/ReadKey/ReadKey.bundle' for m"...) called at /System/Library/Perl/5.30/darwin-thread-multi-2level/DynaLoader.pm line 197
DynaLoader::bootstrap("Term::ReadKey") called at ReadKey.pm.PL line 515
Creating ReadKey.pm
Bootstrapping the XS for blockoptions: make: *** [ReadKey.pm] Error 255
If reporting this issue please do so at (not Homebrew/brew or Homebrew/core):
https://github.com/philpennock/homebrew-protocols/issues
I do not have a clue of what is going on and I will probably going to use a different tool, maybe this report helps anyways.
The text was updated successfully, but these errors were encountered:
I no longer use macOS, so can't easily debug myself.
The second issue is macOS hardening not liking how Perl is installing the module.
The first issue, if I had to guess, is Homebrew only supporting newer versions of Readline?
At some point, I'm going to have to rewrite this tool into a modern language, to be sanely packaged and not be fighting these issues. I'll leave this issue open, but there's nothing I can do to debug macOS issues any more, sorry.
Following the instructions in the README.md I got two issues:
Readline not found
Error 255
I do not have a clue of what is going on and I will probably going to use a different tool, maybe this report helps anyways.
The text was updated successfully, but these errors were encountered: