|
From: | Charles Wilson |
Subject: | Re: cygwin dlopening backends |
Date: | Sun, 13 Nov 2005 00:42:06 -0500 |
User-agent: | Mozilla Thunderbird 1.0.6 (Windows/20050716) |
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 expected tests in the suite.
Then I got ambitious, and did the following: (1) modified ltdl.m4 so that ONLY loadlibrary loader is built for cygwin. (a) bootstrap/conf/build/ran the entire testsuite. all pass.(b) created a new builddir on a managed mount. repeat as above -- all pass.
(2) modified ltdl.m4 so that ONLY dlopen loader is built for cygwin. (a) bootstrap/conf/build/ran the entire testsuite. all pass.(b) created a new builddir on a managed mount. repeat as above -- all pass.
So it seems that, from a functional standpoint, Ralf's patch addresses all of points (1), (2), and (3) from his earlier post.
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 wouldn't be a cygwin-specific hack), but it seems like it could be really complicated.
-- Chuck
[Prev in Thread] | Current Thread | [Next in Thread] |