Hi Eric,
First, let me thank you for excellent and quick review!
* Eric Blake wrote on Sun, Nov 13, 2005 at 05:50:31AM CET:
Ralf Wildenhues Ralf.Wildenhues at gmx.de writes:
I'm not so sure whether we should register/free the thing in loadlibrary
every time instead of once at the start:
Ralf Wildenhues wrote:
Hi Charles,
That just leaves Eric's comments, and Ralf's point (4). I wonder if it
would be a good idea to add --enable/--disable configure flags for every
loader...with the default set of loaders determined on a per-platform
basis. That's the most flexible (and
Charles Wilson wrote:
No, I think the wrong-order problem was because of my (now abandoned)
patch when packaging libtool for the cygwin distribution. I *believe*
the current impl, when both loaders are compiled in, calls dlopen first.
But I'll check...
Hmm.
The behavior I see is odd.
Hi Charles, Eric,
* Charles Wilson wrote on Thu, Nov 10, 2005 at 05:55:28AM CET:
What interface id should loadlibrary.c's vm_open() itself use?
loadlibrary.c is not itself a module...or is it?
Yes, it is. In CVS HEAD, it's a dlpreloaded (static) module.
Note that most of the args
Hi Charles, Eric,
* Charles Wilson wrote on Thu, Nov 10, 2005 at 05:55:28AM CET:
Ralf Wildenhues wrote:
There are several separate issues here:
1) lt_dlhandle_iterate breakage of loadlibrary.c
2) needed dlinterface_free (or maybe _unregister?)
including documentation
3) cygwin
Ralf Wildenhues Ralf.Wildenhues at gmx.de writes:
Hi Charles, Eric,
Hi Ralf,
* Charles Wilson wrote on Thu, Nov 10, 2005 at 05:55:28AM CET:
Ralf Wildenhues wrote:
There are several separate issues here:
1) lt_dlhandle_iterate breakage of loadlibrary.c
2) needed
Ralf Wildenhues wrote:
Please take a look at and test the following patches which should
address (1), (2), and (3). I have not done a lot testing myself /yet/,
so beware.
Basic libtool-HEAD with this patch on cygwin (compiling in both dlopen
and loadlibrary loaders) compiles and passes all
