Created
September 30, 2009 23:09
-
-
Save indirect/198544 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[andre ~/sw/homebrew](ruby-readline)$ brew install readline | |
==> Downloading ftp://ftp.cwru.edu/pub/bash/readline-6.0.tar.gz | |
File already downloaded and cached | |
==> Patching | |
patching file support/shobj-conf | |
Hunk #1 succeeded at 152 with fuzz 2. | |
==> ./configure --prefix=/usr/local/Cellar/readline/6.0 --mandir=/usr/local/Cellar/readline/6.0/share/man --infodir=/usr/local/Cellar/readli | |
==> make install | |
==> Caveats | |
readline is keg-only. This means it is not symlinked into Homebrew's | |
prefix. The formula provides the following rationale: | |
OS X provides the BSD Readline library. In order to prevent conflicts when | |
programs look for libreadline we are defaulting this GNU Readline installation | |
to keg-only. | |
Generally there are no consequences of this for you, however if you build your | |
own software and it requires this formula, you may want to run this command to | |
link it into the Homebrew prefix: | |
brew link readline | |
==> Summary | |
/usr/local/Cellar/readline/6.0: 28 files, 1.0M, built in 20 seconds | |
[andre ~/sw/homebrew](ruby-readline)$ file /usr/local/Cellar/readline/6.0/lib/libreadline.dylib | |
/usr/local/Cellar/readline/6.0/lib/libreadline.dylib: Mach-O universal binary with 3 architectures | |
/usr/local/Cellar/readline/6.0/lib/libreadline.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64 | |
/usr/local/Cellar/readline/6.0/lib/libreadline.dylib (for architecture i386): Mach-O dynamically linked shared library i386 | |
/usr/local/Cellar/readline/6.0/lib/libreadline.dylib (for architecture ppc): Mach-O dynamically linked shared library ppc |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment