[Peeweelinux] Glibc linked binary

[peeweelinux@adis.on.ca]

>ashley@smartsw.co.uk wrote:
>> 
>> Thanks for your reply on the ramdisk thread Troy, it worked a treat :)
>
>Awesome. ;)
>
>> Is there a way of fudging the library dependencies of the macromedia released plugin so that it will work?
>
>Yeah, it is a mammoth job. If I run ldd on my local flash plugin .so, I see:
>
>libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x4039c000)
>libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
>
>So my gut instinct is that you can't fudge it -- the binary *is* looking 
>for the c++ libs by name, but the c lib by symlink. If you could somehow 
>get the flash plugin to look for something like 'libc-2.3.2.so' you'd 
>have a chance, but not likely. :(
>
>-te
>
>-- 
>Troy Engel | Systems Engineer
>Fluid, Inc | http://www.fluid.com

Well I can't rename the symlinks for the libraries libflashplayer.so needs because this breaks other bits of the system. I also tried setting LD_LIBRARY_PATH for a completely serperate lib directory with the correct libraries in. 

So ditch the idea of fudging it :(

The only option I can see then is upgrading the glibc to a 2.2.x version. Not quite sure where to start going about this, it's quite a major job! 

Any ideas?

The best I can think of so far is to build the new glibc sources in a clean directory on my dev machine and then create a peewee package and use this instead of the glibc that is included with peeweelinux? Something tells me that there are complex dependencies and this will require me adding other pieces to the system as well (such as binutils maybe?).

Have a good weekend all,

Thanks again in advance for any help

Ashley Rolleston
Software Engineer
ashley AT smartsw DOT co DOT uk