[mpich-discuss] mpich-3.0.4: building shared libraries w/cygwin
Brad Aagaard
baagaard at usgs.gov
Fri May 10 19:34:44 CDT 2013
On 05/10/2013 05:26 PM, Pavan Balaji wrote:
>
> On 05/08/2013 07:06 PM US Central Time, Brad Aagaard wrote:
>> On 05/06/2013 05:45 PM, Pavan Balaji wrote:
>>>
>>> On 05/02/2013 04:36 PM US Central Time, Brad Aagaard wrote:
>>>> What configure/make arguments should I use to build shared libraries on
>>>> cygwin?
>>>
>>> Just use --enable-shared without any additional --enable-sharedlibs
>>> argument. You might also want to give --disable-static if you don't
>>> want static libraries.
>>>
>>
>> Dropping --enable-sharedlibs from configure gives me the same result as
>> when I use --enable-sharedlibs=libtool or
>> --enable-sharedlibs=gcc-cygwin. I end up with static libraries and no
>> shared libraries even though I also use --enable-shared --disable-static.
>
> This is strange.
>
>> Is there a way to check the Makefile or libtool to see why it doesn't
>> want to build shared libraries?
>
> You could look through the config.log files to see what's going on.
As shown in the config.log that I attached in my original email, all of
the tests for shared libraries give a result of "yes". I am pretty sure
this is related to weak symbols on cygwin and libtool. How libtool
decides to build shared libraries seems pretty opaque to me.
Has building shared libraries for mpich-3.0.4 been tested on cygwin? If
so, what were the configure parameters and what version of cygwin was used?
Thanks,
Brad
More information about the discuss
mailing list