RubyCocoa 0.11.1

[Ryan Schmidt]

On Jul 13, 2007, at 16:54, Eloy Duran wrote:

>> The path /Developer/SDKs/MacOSX10.4u.sdk/opt/local/lib/libz.1.dylib
>> is wrong, to be sure. It should be looking in /opt/local/lib/libz.
>> 1.dylib. I believe I read that it means someone is interpreting the -
>> isysroot parameter incorrectly, but I didn't get to the final
>> solution. But if you search Google for the following two quoted
>> strings you'll see many other instances of the problem.
>>
>> "can't open dynamic library" "/Developer/SDKs"
>>
>> Perhaps one of those threads indicates the solution.
>>
>> http://www.google.com/search?hl=en&q=%22can%27t+open+dynamic+library%
>> 22+%22%2FDeveloper%2FSDKs%22&btnG=Search
>
> I think this one sums it all up:
> http://lists.apple.com/archives/darwin-dev/2006/Apr/msg00042.html
>
> And guess what..... It builds yihaa!
> So thanks for the pointer.
>
> But then this raises the question off how to accomplish this with
> macports. As in:
>
> Should I create a symlink in pre-build like:
> $ ln -s /opt /Developer/SDKs/MacOSX10.4u.sdk/opt
> And then remove it in post-build?
>
> Or should this be created at installation time of macports?
> Because like you said, that search yields a lot more than one  
> result....

MacPorts should not be modifying things outside of /opt, certainly  
not the contents of a Mac OS X SDK. This is a workaround, not a real  
solution.