Help Installing Foundry framework on MacOS Big Sur

[rohgaj6809]

Hi,
I am trying to install the framework Foundry on my computer for testing smart contracts. My computer is a macOS Big Sur laptop, version 11.7.10.

1. So far, I have copied and pasted into my Mac terminal the following code:

curl -L https://foundry.paradigm.xyz/ | bash

2. After pasting this to Mac terminal, I then got the following output:

% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 1942 100 1942 0 0 4064 0 --:--:-- --:--:-- --:--:-- 4064
Installing foundryup...
######################################################################## 100.0%

warning: libusb not found. You may need to install it manually on MacOS via Homebrew (brew install libusb).
Detected your preferred shell is zsh and added foundryup to PATH. Run 'source /Users/macbookair/.zshenv' or start a new terminal session to use foundryup.

3. So the next thing I do is try to install Homebrew by pasting the following into terminal:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)”

4. Then I run the next two commands in terminal to add Homebrew to my PATH:

(echo; echo ‘ eval “$(/opt/homebrew/bin/brew shellenv) ” ‘ ) > > /Users/easyosx/ .zprofile

eval “ $ ( /opt/homebrew/bin/brew shellenv ) "

5. I then do brew upgrade after this and get the following output:

Warning: You are using macOS 11.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.

6. I am unclear where to go from here.