Fix rlwrap on 10.7.4

[arlolra]

I was having trouble installing rlwrap. I had to specify readline.6.2 to get it working. brew doctor says raring to brew.

My system information:

HOMEBREW_VERSION: 0.9
HEAD: 287f5de
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CELLAR: /usr/local/Cellar
CPU: quad-core 64-bit sandybridge
OS X: 10.7.4
Kernel Architecture: x86_64
Xcode: 4.3.3, CLT 1.0.0.9000000000.1.1249367152
GCC-4.0: N/A
GCC-4.2: build 5666
LLVM: build 2336
Clang: 3.1 build 318
MacPorts or Fink? false
X11: /usr/X11
System Ruby: 1.8.7-357

Hope it helps someone.

[2bits]

Nice one. I get the same error, but I don't understand why the fix you made works when libreadline.dylib exists and I have the right LDFLAGS

LDFLAGS='-L/usr/local/Cellar/readline/6.2.2/lib -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk/usr/include -L/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk/usr/lib -L/usr/local/lib'

$ ls -l /usr/local/Cellar/readline/6.2.2/lib/libread*
-r--r--r--  1 nibbles  admin  417164 Jun 13 02:45 /usr/local/Cellar/readline/6.2.2/lib/libreadline.6.2.dylib
lrwxr-xr-x  1 nibbles  admin      21 Jun 13 02:45 /usr/local/Cellar/readline/6.2.2/lib/libreadline.6.dylib -> libreadline.6.2.dylib
-r--r--r--  1 nibbles  admin  678440 Jun 13 02:45 /usr/local/Cellar/readline/6.2.2/lib/libreadline.a
lrwxr-xr-x  1 nibbles  admin      21 Jun 13 02:45 /usr/local/Cellar/readline/6.2.2/lib/libreadline.dylib -> libreadline.6.2.dylib

Any idea?

[arlolra]

My guess is that the linker gets confused with /usr/lib/libreadline.dylib -> libedit.3.dylib. Specifying readline.6.2 forces it to choose the right one.

[2bits]

@adamv @jacknagel please review when you're free. @arlolra thanks for clearing that up. I forgot to inspect /usr/lib and missed that.

[adamv]

Pretty sure this is related to the Xcode/CLT change we pulled, since everything fails to link against readline now. Need to fix the root cause.

[adamv]

Please brew update and retry without this patch; #13037 has been pulled and should address this issue.

[arlolra]

Yup, seems to work. Thanks @adamv