all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Keith David Bershatsky <esq@lawlist.com>
To: Eli Zaretskii <eliz@gnu.org>
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 00:00:13 -0700	[thread overview]
Message-ID: <m2twq9pxfm.wl%esq@lawlist.com> (raw)
In-Reply-To: <m2vbasg27x.wl%esq@lawlist.com>

I tracked down another build discrepancy this evening relating to a failure to find `iconv.h`.  It is caused because the default new installation of MinGW comes with a later version of libiconv than used by ezwinports.  I am pretty certain the error comes about when adding `cairo-1.12.16-w32-bin.zip` from ezwinports for the purposes mentioned in the `.../emacs/nt/INSTALL` readme file.  It might be caused by adding `p11-kit-0.9-w32-bin.zip` or `pkg-config-0.28-w32-bin.zip`, but I don't think so.  I have run so many builds recently, it's hard to keep track.

I think the process of installing packages with MingGW has changed since the early days when the `.../emacs/nt/INSTALL` was written.  There are references on the internet about placing the archives into the main root MinGW directory and they will supposedly be recognized automatically; however, the current installer seems to be using `C:\mingw\var\cache\mingw-get\packages` for storing the default repositories.  Placing the ezwinports dependencies into the MinGW root directory or the latter packages directory is insufficient for the old libiconv to be seen as an available install in the graphical installation utility for MinGW.  After a ton of Googles, I came up with the following to remove the repository default of 1.14-3 and replace it with the older version:

c:\mingw\bin\mingw-get remove mingw32-libiconv

c:\mingw\bin\mingw-get install "libiconv=1.13.1-1"

The result is that the Emacs build no longer fails for failure to find `iconv.h`.

I'm not sure how the issue above should be dealt with, but it certainly was time consuming tracking it down.


On a different note, I haven't been able to configure `guntls` so that it shows up automatically as an available "yes" Emacs install following a plain `./configure --prefix=/my/path`.  I have extracted all of the following from ezwinports to the MinGW root:

gnutls-3.3.11-w32-bin.zip
p11-kit-0.9-w32-bin.zip
pkg-config-0.28-w32-bin.zip
gdk-pixbuf-2.30.2-w32-bin.zip
giflib-5.1.0-w32-bin.zip
glib-2.38.2-w32-bin.zip
jpeg-v9a-w32-bin.zip
libpng-1.6.12-w32-bin.zip
librsvg-2.40.1-2-w32-bin.zip
libxml2-2.7.8-w32-bin.zip
tiff-4.0.3-w32-bin.zip
zlib-1.2.8-2-w32-bin.zip
libXpm-3.5.11-w32-bin.zip
cairo-1.12.16-w32-bin.zip

Any ideas on how to make the guntls option show up as `yes` when running `./configure` would be greatly appreciated.  Perhaps it's another dependency issue where something in MinGW is newer and needs to be downgraded?

Thanks,

Keith





  parent reply	other threads:[~2015-10-02  7:00 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=m2twq9pxfm.wl%esq@lawlist.com \
    --to=esq@lawlist.com \
    --cc=21590@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.