Description
brew gist-logs <formula>
link OR brew config
AND brew doctor
output
Nothing suspicious related to this issue — all good.
Verification
- My
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue. - I ran
brew update
and am still able to reproduce my issue. - I have resolved all warnings from
brew doctor
and that did not fix my problem. - I searched for recent similar issues at https://github.com/Homebrew/homebrew-core/issues?q=is%3Aissue and found no duplicates.
What were you trying to do (and why)?
I am trying to use the picotool
installed from homebrew to build all pico-examples for the RP2350 chip used in Raspberry Pico 2 boards (export PICO_PLATFORM="rp2350"
).
Homebrew picotool
claims to be version 2.1.1:
picotool v2.1.1 (Darwin, AppleClang-16.0.0.16000026, Release)
(output of picotool version
installed from homebrew)
Note that the RP2350 chip takes advantage of a couple more recent features integrated into the picotool
.
What happened (include all command output)?
The homebrew installation of picotool
, despite claiming to be version 2.1.1, does not support the full feature set of that version as it is available on the respective picotool
GitHub release page: https://github.com/raspberrypi/picotool/releases
In particular, the feature picotool seal ...
is not supported (there may be others). Try and run picotool help seal
with the homebrew installation, which produces an error that the seal
subcommand is not known. This means that pico-examples
cannot be (fully) compiled for the new RP2350 chip, unless one does a manual build and install of picotool
which has some pitfalls by itself due to cmake
quirkiness.
The homebrew formula seems to obtain its 2.1.1 release via the link: https://github.com/raspberrypi/picotool/archive/refs/tags/2.1.1.tar.gz
(See respective formula at time of writing: https://github.com/Homebrew/homebrew-core/blob/2caa6d1734f371ccc56f3f8724878db49b9dabe2/Formula/p/picotool.rb)
I suspect that the link points to something that is currently not quite up to date, per current 2.1.1 release of picotool
on https://github.com/raspberrypi/picotool/releases.
Thanks very much for the formula author(s) to look into this and bump the .tar.gz
to the actual 2.1.1 release.
What did you expect to happen?
That picotool
from homebrew will support all features of the 2.1.1 release per GitHub release: https://github.com/raspberrypi/picotool/releases. E.g., if I do a custom build of 2.1.1 from the picotool release page, we ought not see any different to the homebrew installation of picotool
.
Step-by-step reproduction instructions (by running brew
commands)
brew install picotool
picotool help seal
# This ought produce the abovementioned error.