On Sat, Jun 25, 2011 at 05:05:01PM +0200, Alexandre Ratchov wrote:
> On Sat, Jun 25, 2011 at 03:03:33PM +0200, Marc Espie wrote:
> > On Sat, Jun 25, 2011 at 12:52:02PM +0200, Alexandre Ratchov wrote:
> > > There's code (eg. audio/openal, but not only) that does:
> > >
> > > dlopen("libsndio.so", ...);
> > >
> > > and then calls dlsym() for each function and so on. What's the point
> > > of doing this instead of simply linking the binary with -lsndio and
> > > using functions normally?
> > >
> > > hints?
> >
> > Misplaced portability concerns from upstreams, and ETOOMUCHWORK from the
> > porter.
> >
> > If it's not too intrusive, telling upstream to forget about old OpenBSD
> > versions and doing the normal linking thing is the way to go.
>
> but how using dlopen() would help old OpenBSD versions? do upstream
> thinks we ship old .so files in base?
When dlopen() fails, you can try something else. Whereas linked programs
fail to start.
