From: craigslist <craigslist@...>
Date: 2006-10-25T10:04:16+09:00
Subject: Re: zlib.so Problem on MIPS target platform.


On Oct 24, 2006, at 8:50 PM, Aredridel wrote:

>> Unable to resolve symbol. Ok, that leads me to believe there is a
>> problem with the library i just built from zlib-1.2.1. I have
>> installed libz.so.1.2.1. Checking the dependencies on libz.so.1.2.1,
>> i can see that all required dependencies are available and it is
>> properly linked to uclibc. Included in the zlib-1.2.1 package are two
>> test applications, minigzip and example. Both test apps run perfectly
>> on the target platform with the newly created libz.so.1.2.1 library.
>> So it seems that the library is functioning correctly and ruby is
>> able to FIND the library. But it fails to load within ruby.
>
> Do note that zlib.so is the ruby extension, but libz.so.foo is the  
> zlib
> library. They're not the same thing. Sounds like you have a zlib.so
> linked against another libz, but that's a guess.
>
> Aria

so...zlib.so extension IS required by ruby? I thought I had read  
somewhere that the zlib.so extension was deprecated after 1.6. 
(something). And I could simply use the libz.so from the system.

Currently, I simply have ln -s /usr/lib/libz.so.1.2.1  /usr/local/lib/ 
ruby/1.8/mipsel-linux/zlib.so .... so, just a link to the systems  
libz. Is that the problem? And if so...does it matter whether i use  
the included ruby/ext/zlib or the ruby-zlib-0.6.0 package? Are they  
the same thing? (Besides the fact that I can't seem to get either to  
cross compile correctly without some major tweaking).

Stefan Willmert