unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: 21590@debbugs.gnu.org
Subject: bug#21590: 25.0.50; MS-Windows; fns.c:4863:21: error: 'MD5_DIGEST_SIZE' undeclared (first use in this function)
Date: Fri, 02 Oct 2015 20:59:23 +0300	[thread overview]
Message-ID: <83bnch5eys.fsf@gnu.org> (raw)
In-Reply-To: <m2612ptg6q.wl%esq@lawlist.com>

> Date:  Fri, 02 Oct 2015 08:59:09 -0700
> From:  Keith David Bershatsky <esq@lawlist.com>
> Cc:  21590@debbugs.gnu.org
> 
> The advice by Eli on looking at the `config.log` to track down why gnutls was not available worked like a charm.  It told me that I was missing both `libtasn1` and `nettle`.  I downloaded and extracted `libtasn1-4.2-w32-bin.zip` and `nettle-2.7.1-w32-bin.zip` from ezwinports and now gnutls is detected during the configure and it says "yes" by default.

I guess you were missing the header files from these 2 libraries.

> I didn't see any mention in the `gnutls` section of the `../emacs/nt/INSTALL` readme about the prerequisites of the above-mentioned two libraries `libtasn1` and `nettle`, so my suggestion would be to include a mention, and maybe even something about checking the `config.log` if there seems to be a problem.

Will do.

> The newer version of libiconv (i.e., 1.14-3) does not use `iconv.h`, so that is why the prior attempts at building emacs failed -- i.e., `missing` the file.  Downgrading libiconv to 1.13.1-1 produces the required `iconv.h`, and that resolves the error message regarding the missing header file.
> 
> The version of `libintl` installed in MinGW is 0.18.3.2-2 -- `mingw32-libintl`, which traces to mingw32-gettext.  What version, please, should I be using (so that I can locate and downgrade if needed)?

The one you find here:

  https://sourceforge.net/projects/ezwinports/files/Dependencies/





  reply	other threads:[~2015-10-02 17:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30  0:50 bug#21590: 25.0.50; MS-Windows; fns.c:4863:21: error: 'MD5_DIGEST_SIZE' undeclared (first use in this function) Keith David Bershatsky
2015-09-30  1:34 ` Glenn Morris
2015-10-01  6:36   ` Eli Zaretskii
2015-09-30  4:04 ` Keith David Bershatsky
2015-10-01  7:00   ` Eli Zaretskii
2015-09-30 21:26 ` Keith David Bershatsky
2015-10-01  6:45   ` Eli Zaretskii
2015-10-01 15:54   ` Eli Zaretskii
2015-10-02  8:36   ` martin rudalics
2015-10-02  8:51     ` Eli Zaretskii
2015-10-02  9:00       ` martin rudalics
2015-10-02  9:09         ` Eli Zaretskii
2015-10-01  5:02 ` Keith David Bershatsky
2015-10-01 22:15 ` Keith David Bershatsky
2015-10-02  6:45   ` Eli Zaretskii
2015-10-02  7:00 ` Keith David Bershatsky
2015-10-02  8:00   ` Eli Zaretskii
2015-10-02  7:17 ` Keith David Bershatsky
2015-10-02  8:10   ` Eli Zaretskii
2015-10-02 15:59 ` Keith David Bershatsky
2015-10-02 17:59   ` Eli Zaretskii [this message]
2015-10-06 18:33 ` Keith David Bershatsky
2015-10-06 18:45   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83bnch5eys.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21590@debbugs.gnu.org \
    --cc=esq@lawlist.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).