how could a symlink from one version to a different one be left in /opt/homebrew/opt #6277
Unanswered
190n
asked this question in
Everyday usage
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Output of
brew config
Output of
brew doctor
Description of issue
I work for https://github.com/oven-sh where we have many Macs with Homebrew installed and use LLVM 19 to compile our C++ code. At various times on different machines, Homebrew has created a symlink from the
llvm@19
prefix to thellvm@20
one:I feel pretty strongly that there is some Homebrew bug here -- it should never create a symlink like that. But so far I haven't been able to reproduce this situation starting from a fresh Homebrew install, so I don't know how to report it.
On this particular machine, I know that we previously had pinned
llvm@19
and also had an old Rust version installed that depended on LLVM 19. Upgrading Rust was blocked because the new version would require the LLVM version be upgraded to 20. The last commands ran were:Unpinning LLVM turned out to be a mistake since we actually need to keep version 19 too. But that should have left us with
/opt/homebrew/opt/llvm@19
deleted, not changed to point to version 20.I did try to reproduce this situation on a fresh VM, by:
homebrew/core
and reverting the repository to Homebrew/homebrew-core@2511b1a (when Rust 1.86, the last version to use LLVM 19, was added)But I always observed that
/opt/homebrew/opt/llvm@19
was either preserved with the right version, or deleted. I couldn't recreate the situation where it is a symlink to the wrong version.Has anyone else observed this issue, or does anyone have ideas for what commands might lead to this situation?
Beta Was this translation helpful? Give feedback.
All reactions