[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Help-gnutls] Re: gnutls 2.3.4 doesn't copile using MinGW
From: |
Simon Josefsson |
Subject: |
[Help-gnutls] Re: gnutls 2.3.4 doesn't copile using MinGW |
Date: |
Wed, 16 Apr 2008 12:50:54 +0200 |
User-agent: |
Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (gnu/linux) |
Massimo Gaspari <address@hidden> writes:
> Simon Josefsson wrote:
>> Massimo Gaspari <address@hidden> writes:
>>
>>
>>> In the meantime I recompiled libgcrypt using
>>>
>>> ./configure --disable-shared --disable-asm --enable-random=w32
>>> --disable-dev-random
>>>
>>> Do you think that the "random" options are correct to use the library
>>> in a Windows environment (not using MinGW)?
>>>
>>
>> Yes. I would think that the script will guess these values
>> automatically though, so you probably don't need to specify them. If it
>> guesses the w32 module properly, the --disable-dev-random flag won't
>> matter since the w32 module doesn't use /dev/random.
>>
>> Does building fail if you remove --disable-asm? You may get a speed
>> improvement if you remove it, but removing it can also cause build
>> failures.
>>
>> /Simon
>>
> I tried to compile libgcrypt without --disable-shared and I didn't
> observe any compilation issue. Moreover the make check was
> successfully.
What about doing the same for GnuTLS builds too? Chances are that
you'll get static libraries out of it that builds, at least I do using
MinGW under linux.
> Anyway I switched back to --disable-asm.
I'm not sure I understand -- did you get errors if you removed it?
/Simon
[Help-gnutls] Re: gnutls 2.3.4 doesn't copile using MinGW, Massimo Gaspari, 2008/04/14