[tahoe-dev] Installation on MacOS failed

Richard Johnson rjohnson+tahoe-dev at ucar.edu
Fri Apr 5 17:35:13 UTC 2013

clang is likely missing from the default $PATH because Apple separated out
a number of command line tools, including clang, after Xcode 4 release.

While they're still present inside various packages within Xcode, they
move around between releases.

A web search for 'command line tools for xcode' should yield instructions
for downloading and installing from within Xcode.

The command line tools download will put clang and other binaries in
directories typically included in the default $PATH.


On April 3, 2013 6:33:21 AM "Zooko Wilcox-O'Hearn" <zooko at zooko.com> wrote:
> Hello! Thank you for the bug report. This is an instance of
> https://tahoe-lafs.org/trac/tahoe-lafs/wiki/FAQ#Q26_compile_error
> https://tahoe-lafs.org/trac/tahoe-lafs/wiki/CompileError
> I'll edit the wiki to give the typical error message on Mac OS X.
> > unable to execute clang: No such file or directory
> So, your friend could either install the compiler ("clang"), or someone who
> has Mac OS X and a compiler could build a pycryptopp package (a Python
> "egg") for him. If someone does the latter, please share it with us so we
> can add it to this chart:
> https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html
> What version of Python does your friend have?
> Hm, you said that he had xcode. I wonder why he doesn't have a "clang"
> executable in his path, then...
> Regards,
> Zooko

More information about the tahoe-dev mailing list