#17

i am not sure about all that but i tried to instigate terminal to spit responses and the following was what happened:
"Last login: Sun Jun 21 13:53:02 on console
williams-iMac:~ williamcloyd$ which brew
williams-iMac:~ williamcloyd$ which dfu-programmer
williams-iMac:~ williamcloyd$ "

#18

which begs the question: how to set up homebrew path variable?

as i said, this stuff is black magic for me and the instal guide to get this far does not mention any of these steps afaik.

the help is super appreciated!

#19

Is this what you pasted into terminal:

ruby -e “$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)”

What do you get when you type the following and hit Enter:

echo $PATH

#20

/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin

#21

That looks correct. And what happens when you paste this in and hit enter?

ruby -e “$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)”

#22

i will try this in a sec.
do you mean to enter the whole second line of your message? i did try that the first time but there was a weird “1” character near the end that might have been troublesome. anyway, hopefully this time something good happens, either way i will post what it tells me.

i wonder if an older operating system would be more advantageous. like i could try all this on a 10.6.8 machine if it would help to produce a successful updating procedure.

#23

==> This script will install:
/usr/local/bin/brew
/usr/local/Library/…
/usr/local/share/man/man1/brew.1
==> The following directories will be made group writable:
/usr/local/.
/usr/local/include
/usr/local/lib
/usr/local/lib/pkgconfig
==> The following directories will have their group set to admin:
/usr/local/.
/usr/local/include
/usr/local/lib
/usr/local/lib/pkgconfig

Press RETURN to continue or any other key to abort

#24

so it appears i got further. but it definitely did not update the module. homebrew looks to be successfully installed but the following is what happens when i double-click the firmware (yes i know it is white whale. i am trying to start with WW).
Last login: Mon Jun 22 20:28:19 on ttys001
williams-iMac:~ williamcloyd$ /Users/williamcloyd/Desktop/whitewhale-1/flash.command ; exit;
/Users/williamcloyd/Desktop/whitewhale-1/flash.command: line 3: dfu-programmer: command not found
/Users/williamcloyd/Desktop/whitewhale-1/flash.command: line 4: dfu-programmer: command not found
/Users/williamcloyd/Desktop/whitewhale-1/flash.command: line 5: dfu-programmer: command not found
logout

[Process completed]

#25

Right, so now you need to install dfu-programmer. Type:

brew install dfu-programmer

And hit enter. Then try to update the firmware again.

#26

i really thought i did though. i will try again.

this whole process really lowers my self-esteem.

#27

yeah i had done it earlier. this was what it said.
==> /usr/bin/sudo /usr/bin/chgrp admin /usr/local/. /usr/local/include /usr/local/lib /usr/local/lib/pkgconfig
==> /usr/bin/sudo /bin/mkdir /Library/Caches/Homebrew
==> /usr/bin/sudo /bin/chmod g+rwx /Library/Caches/Homebrew
==> Downloading and installing Homebrew…
==> Installation successful!
==> Next steps
Install the Command Line Tools for Xcode: https://developer.apple.com/downloads
Run brew help to get started
williams-iMac:~ williamcloyd$ brew install dfu-programmer
Warning: No developer tools installed.
You should install the Command Line Tools.
The standalone package can be obtained from
https://developer.apple.com/downloads
or it can be installed via Xcode’s preferences.
==> Installing dependencies for dfu-programmer: libusb, libusb-compat
==> Installing dfu-programmer dependency: libusb
==> Downloading https://homebrew.bintray.com/bottles/libusb-1.0.19.mountain_lion
######################################################################## 100.0%
==> Pouring libusb-1.0.19.mountain_lion.bottle.1.tar.gz
sh: -L: invalid option
Usage: sh [GNU long option] [option] …
sh [GNU long option] [option] script-file …
GNU long options:
–debug
–debugger
–dump-po-strings
–dump-strings
–help
–init-file
–login
–noediting
–noprofile
–norc
–posix
–protected
–rcfile
–restricted
–verbose
–version
–wordexp
Shell options:
-irsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o option
Error: Failure while executing: -L /usr/local/Cellar/libusb/1.0.19/lib/libusb-1.0.0.dylib
Warning: Bottle installation failed: building from source.
Error: libusb cannot be built with any available compilers.
To install this formula, you may need to:
brew install gcc
williams-iMac:~ williamcloyd$

#28

tried again.

o install this formula, you may need to:
brew install gcc
williams-iMac:~ williamcloyd$

#29

then i did try brew install gcc

i feel like i am going to blow up my computer.

#30

Don’t panic!

Nothing’s going to blow up. Did you try installing the ‘Command Line Tools’ as suggested in the message above?

#31

i installed the brew install gcc
not sure if that is the command line stuff. then retried the firmware install. no different. will try again tonight if i get time.

#32

are there any specific ways to install ‘Command Line Tools’? do i literally type that into terminal or is it the “brew install gcc”?

#33

Go there and search for command line tools. you probably have to log in with an apple id. Otherwise you can probably download from the App Store. NB: I’m not entirely sure this is what you need, but that’s what terminal told you, so I’d go with that!

Also ‘gcc’ is a compiler which you don’t need to do the update. It seems the install failed to find the right option for your OS, so tried to compile the source files (hence asking for gcc). Try the Command Line Tools first and run the brew command again before going down that path.

#34

ok, i think that worked. tried the updating process and each seemed to work. not sure how to tell each (earth sea and white whale) too the updates but i think it worked.

thanks so much for the handholding and sorry for my idiocy.

#35

The good news is, that once you have all these pieces on your laptop, then future updates involve just opening the script file that comes with the update document. And it does the whole thing automatically, so you will not need to worry about doing all this again! :smile:

1 Like
#36

what is the easiest in live use determining factor of firmware for earthsea and white whale. i am slightly paranoid since last night that the firmware updates might not have worked. i am pretty confident that what whale worked as it loads a different set of info on startup than it did before… but earthsea, i just can’t tell. if installs did work then i think earthsea is 1.1 and white whale is 1.4. i think… i hope…

i am super excited to dig into these once i get more time, if i ever get more time.