Closed crgibbons closed 1 month ago
I'm confused about why your brew is downloading bottles for ventura rather than arm64_ventura
or arm64_sonoma
. Maybe we can build topcom
locally. This should be quick. Try the following:
brew remove topcom --ignore-dependencies
brew install --build-bottle topcom
(if this failed, try without --build-bottle
)
Then try installing (or upgrading) M2 again.
If this doesn't help, could you add the output of brew config
and brew doctor
?
Oh, could you also show me the following:
cd $(brew --repo macaulay2/tap)
git show --summary
Show and tell from the summary (before trying the fix)
commit 48a482b5667670114352307402e04e7ca8cca34e (HEAD -> main, origin/main, origin/HEAD)
Author: Mahrud Sayrafi <mahrud@umn.edu>
Date: Fri Oct 4 02:33:02 2024 +0000
givaro: update 4.2.0_1 bottle.
Reinstalling topcom did the trick. (FWIW, this is a new install, not an upgrade of a previous install)
Great! Your brew is up to date. I'm not sure what happened ...
FWIW, this is a new install, not an upgrade of a previous install
Is it possible that your laptop had synced everything in the cloud, including the old M2? This is the line that makes me suspect this may have happened:
==> Upgrading macaulay2/tap/m2
1.19.1_3 -> 1.24.05_1
At some point in the past we had a cddlib@0.94m
bottle, but now we just use the cddlib
bottle that is available via Homebrew's own library.
Also, the fact that your brew was downloading x86 bottles worries me that for some your brew might be set to run using the emulator instead of using native arm64 binaries. If this wasn't intentional, you might want to look into it.
Thanks for that - I will take a look and see what's happening with my homebrew set up!
And yes, I think I had gotten synched to the cloud somehow (or via the "smart" transfer from one MacBook on the intel chipset to a new one). I bet that's what's going on with my homebrew, too.
Okay, that makes sense. I'll close this issue for now but let me know if anything else comes up.
@mahrud - I reinstalled brew for the M3 chip and can verify that everything installs smoothly now.
Excellent, thanks for letting me know!
When attempting to install M2 from homebrew, I receive the warning:
To confirm that this was a warning that would prevent M2 from running, I attempted to open M2 from
brew --prefix M2
/bin/M2 but received the following error (for me,brew --prefix M2
evaluates to/usr/local/opt/macaulay2
)More details on the output of
brew install Macaulay2/tap/M2
below.