Closed llimllib closed 10 months ago
With a generous application of DYLD_LIBRARY_PATH
, I can get the program running:
$ DYLD_LIBRARY_PATH=/opt/homebrew/lib:/opt/homebrew/Cellar/protobuf/24.2/lib:/opt/homebrew/Cellar/abseil/20230125.3/lib:/opt/homebrew/Cellar/thrift/0.18.1_1/lib/ gdal_translate --help
Usage: gdal_translate [--help-general] [--long-usage]
<snip rest...>
obviously this is less than ideal though
Can you try checking brew outdated
formulae and retrying any upgrades again?
Your above snippets are showing older versions (e.g. protobuf 24.2
, apache-arrow 13.0.0_2
, etc.).
Your gist claims to have upgraded protobuf
:
==> Pouring protobuf--24.4.arm64_sonoma.bottle.tar.gz
Though it doesn't have pour log for other formulae like apache-arrow
(it did show outdated apache-arrow 13.0.0_2 -> 13.0.0_8
but no info on upgrade attempt) so there may be something odd about versions.
@cho-m Sure, thanks for taking a look. Here's brew outdated
:
And that seems to do it:
What's the proper response to this? Should the formula indicate a minimum version of apache-arrow
?
In theory, brew
should have automatically upgraded those formulae. You can see that it was trying to do so in Gist:
==> Upgrading 31 dependents of upgraded formulae:
Disable this behaviour by setting HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
apache-arrow 13.0.0_2 -> 13.0.0_8, cffi 1.15.1 -> 1.16.0, awscli 2.13.13 -> 2.13.25, curl 8.2.1 -> 8.3.0, emscripten 3.1.45 -> 3.1.46, ghostscript 10.01.2 -> 10.02.0, git 2.40.0 -> 2.42.0, gnuplot 5.4.8_1 -> 5.4.9, gts 0.7.6_2 -> 0.7.6_3, jpeg-xl 0.8.2 -> 0.8.2_1, graphviz 8.1.0 -> 9.0.0, harfbuzz 8.1.1 -> 8.2.1, huggingface-cli 0.16.4_1 -> 0.17.3_1, imagemagick 7.1.1-15 -> 7.1.1-20, llvm 16.0.6 -> 17.0.2, mongosh 1.10.6 -> 2.0.1, mongodb-atlas-cli 1.10.0 -> 1.12.1, neovim 0.9.1 -> 0.9.2, netpbm 11.02.01 -> 11.02.04, node 20.5.1 -> 20.8.0, openai-whisper 20230314 -> 20230918, openjdk 20.0.1 -> 21, php 8.2.9 -> 8.2.11, python@3.11 3.11.5 -> 3.11.6, qt 6.5.1_3 -> 6.5.2, qt@5 5.15.10 -> 5.15.10_1, tesseract 5.3.2_1 -> 5.3.3, unbound 1.18.0 -> 1.18.0_1, vim 9.0.1800 -> 9.0.2000, watchman 2023.08.28.00 -> 2023.10.09.00, yt-dlp 2023.7.6_1 -> 2023.10.7
...
==> Downloading https://ghcr.io/v2/homebrew/core/apache-arrow/manifests/13.0.0_8
########################################################################################################################################### 100.0%
Not sure why it didn't. It could be something with brew
dependency resolution, or something with the JSON API, or something in your environment, etc.
What does env | grep HOMEBREW
say?
$ env | grep HOMEBREW
HOMEBREWBIN=/opt/homebrew/bin
HOMEBREWSBIN=/opt/homebrew/sbin
That's weird that it downloaded but didn't install the apache-arrow package!
I am also having this issue today on arm mac. I have protobuf@24.4 but the apachearrow is referencing 24.2
Upon further reading, I realized that my apachearrow was out of date, after a brew upgrade
, my problem was solved
homebrew seems to be doing this consistently for me. This morning I installed gifski
, and it fails with a dyld error despite the library existing in /opt
.
This is due to https://github.com/Homebrew/brew/pull/16152, thanks to cho-m and Bo98 in #153177 for finding the correct issue
should hopefully be fixed by Homebrew/brew#16152, but apparently if you have an install with a lot of oudated packages those packages may still be broken and will need to be updated/reinstalled if they cause problems. (Or you could update all outdated packages, but I'm never confident enough to try that)
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew doctor
output" saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
install gdal
What happened (include all command output)?
The build succeeded, but calls to gdal fail:
What did you expect to happen?
gdal to run
Step-by-step reproduction instructions (by running
brew
commands)This issue seems like it might be similar to #140082, but that issue suggests that it's fixed in aws-sdk-cpp versions > 1.11.146, however I have 1.11.175 installed.
I'd also note that all those dylibs do exist, just not in any of the directories that get tried: