[csw-maintainers] Some direct binding "side effets"

[Yann Rouillard]

Hi everybody,

FYI, I discovered two sort of side effects with direct binding:

* Chrooted daemons

Direct binding also enables lazy loading. This can cause problem with
chrooted daemons, because they may try to load a library after the
chroot step and, of course, they will not find the .so file in the
chrooted environment (unless you put it on purpose).

One fix is to just disable lazy loading:
 EXTRA_LD_OPTIONS += -z nolazyload

Problem encountered with openssh:
https://www.opencsw.org/mantis/view.php?id=5006

* Problem with GNU strip

Some packages binaries are stripped using GNU strip, usually because
they added /opt/csw/gnu in the path (to help with build systems
requiring GNU tools).
Unfortunately, GNU strip seems to corrupt the elf section added when
direct binding is enabled (bug opened for that:
https://www.opencsw.org/mantis/view.php?id=4994 ).
I don't think it renders the binaries unusable but direct binding
probably doesn't work as elfdump can't properly display the section
anymore.

The solution is to make sure GNU strip is not used. As it can corrupt
a elf section, it's probably not a good idea to use it anyway.
You can usually do this by defining STRIP=/usr/ccs/bin/strip in the
build environment.

Problem encountered with libgnomeprint and ffmpeg.

I added some info about this on the wiki:
http://wiki.opencsw.org/checkpkg-error-tags#no-direct-binding

Yann