Actually, I just remembered: this happened when installing arm-elf-gcc, but the binaries were still there, so I just forgot about it. That's probably why that directory wasn't there, right? (In case you're wondering, I uninstalled and reinstalled arm-elf-gcc, and it happened again, which is how I remembered.)
http://pastebin.com/Nk9c3E6s
If building the toolchain failed, then you have much bigger problems than a directory not existing. Notice the first error:
#
ln sys/crt0.o crt0.o >/dev/null 2>/dev/null || cp sys/crt0.o crt0.o
#
mkdir tmp
#
cp: sys/crt0.o: No such file or directory
#
make[8]: *** [crt0.o] Error 1
Regarding the wiki:
The instructions on the wiki may or may not be wrong (or not applicable to your version of OSX or macports or who knows what, since none of that information is specified) but until you can narrow it down a bit, I don't see how your message could be helpful to anyone. Clearly, it's not just a matter of a mis-typed directory name in the instructions.
I'm not aware of anything like CHDK shell for Mac. Again, the path of least resistance would be to use XP (either on another machine or in a VM) with a chdkshell. I believe there are also pre-built toolchains for linux, but that is less likely to Just Work.
Or you can figure out what your problems are on mac, but it's clear you'll have to do some debugging.