Re: libmap and linuxpluginwrapper

["Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx>]

On 06.04.2004, at 07:34, Matthew Dillon wrote:

> :The linuxpluginwrapper port on FreeBSD-4 and DragonFly requires
> :changes to rtld-elf and configuring /etc/libmap.conf .  This works
> :fine for me on DragonFly (I tested the flash plugin on mozilla-firefox
> :and konqueror).  Is there any reason not to apply this patch to the
> :base system?
>     Hmm.  That's a pretty nasty patch but it looks like FreeBSD 
> brought it
>     into their base system.  I will review the FreeBSD changes and 
> possibly
>     bring it into our base system.

To me, it really looks like a mean hack. Joerg, Andy and me were 
discussing about a similar thing for packages (providing the full 
pathname of a shared object vs rpath etc). My feeling about this is: 
Information about linking should be contained in the ELF itself and not 
be decoupled into a systemwide configuration file:

Add magic to ELF/binutils/rtld to have to possibility to explicitely 
specify the exact shared object file which should be used (as first 
try) to use for this "generic" shared object name (libfoo.so.3). Of 
course this must easily be changeable after final linking (rpath is 
hard to change afterwards because of virtual memory location + 
relocation).

I think this would also be the way to use here: for example, specify in 
/usr/local/lib/linux-flashplugin6/libflashplayer.so to try for the 
requested libstdc++-libc6.2-2.so.3 the file 
/usr/lib/gcc2/libstdc++.so.3 or even /usr/lib/${CCVER}/libstdc++.so. If 
this file doesn't exist, continue searching like before.

cheers
  simon

--
/"\   http://corecode.ath.cx/#donate
\ /
 \     ASCII Ribbon Campaign
/ \  Against HTML Mail and News

Attachment: PGP.sig
Description: This is a digitally signed message part