Re: Putting .so symlinks in libs package for dlopen()ing?

2002-12-11 Thread Andrew Clausen
On Wed, Dec 11, 2002 at 01:06:15AM -0600, Rob Browning wrote: > Timshel Knoll <[EMAIL PROTECTED]> writes: > > > Possible solutions: > > 4. Fix libtool and libltdl to support >lt_dlopen_interface (const char *name, int interface) > and use that. > > This would require modifyin

Re: Putting .so symlinks in libs package for dlopen()ing?

2002-12-08 Thread Andrew Clausen
On Mon, Dec 09, 2002 at 12:16:44AM -0500, Daniel Burrows wrote: > So reiserfs has an internal mechanism for reporting whether stuff > is really compatible? Yes. An internal version numbers policy. You call a function (via dlsym) asking if the interface you (i.e. parted) is using, and reiserfs

Re: Putting .so symlinks in libs package for dlopen()ing?

2002-12-08 Thread Andrew Clausen
Hi again, I forgot to mention: what if a backward-compatible API change is made to libreiser? libtool library versioning is designed to deal with all of this... can we use it somehow? Cheers, Andrew

Re: Putting .so symlinks in libs package for dlopen()ing?

2002-12-08 Thread Andrew Clausen
On Mon, Dec 09, 2002 at 02:02:12AM +, Scott James Remnant wrote: > I don't see why this is a problem, you'd only need to change the > dlopen() code if there's a SONAME change - and that should only change > if there's a binary-incompatible difference. A difference that might > not be picked up