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: Thu, 01 Oct 2015 10:00:44 +0300	[thread overview]
Message-ID: <83y4fn9ioz.fsf@gnu.org> (raw)
In-Reply-To: <m2twqcft7w.wl%esq@lawlist.com>

> Date: Tue, 29 Sep 2015 21:04:35 -0700
> From: Keith David Bershatsky <esq@lawlist.com>
> Cc: 21590@debbugs.gnu.org
> 
> Thank you, Glenn, for the reference to the mail-list archives regarding moving `C:\gnuwin32\include\md5.h` out of the way.
> 
> Building the latest version of Emacs trunk master branch on Windows is by no stretch of the imagination as simple as the first Google search.  There is a reason that only one person in the entire world is posting Windows trunk builds every few weeks -- i.e., building Emacs on Windows is completely beyond the reach of mere mortals, and out of the reach of beginning programmers and hobbyists such as myself (without the assistance of advanced programmers such as you and Eli).

This is somewhat inaccurate.  What _is_ hard is creating a
well-organized MSYS/MinGW development environment.  This is more or
less a one-time effort, and it does take some time, blood and tears.
In effect, you are creating by hand a sophisticated environment that
any Posix system has for you out of the box.  So it's a little wonder
that part is not simple, even before we consider the few Windows
specific tricks one must pull for that environment to be rock-solid.

But once you are through that one-time effort, the actual building of
Emacs presents no problems at all.  It "just works", as on any Posix
system.

We provide detailed instructions for building Emacs in Windows in
nt/INSTALL.  Most of the information in that file is dedicated to that
first step -- creating a stable, coherent development environment.
The experience I and others gained while achieving that goal is
described there, complete with several notable gotchas and how to
avoid them.  It would be good if you could read that file, now armed
with your own experience, and provide feedback, so that the
instructions could be improved where they need improvement.

> I renamed it to `md5.h.off` and tried my luck at building Emacs again, but was met with the error below.  I also tried my luck at building and incorporating into the `mingw` directory the following five (5) libraries -- zlib, giflib, libpng, jpeg and libpng -- in an effort to remove `gnuwin32` from the equation entirely; however, I was met with the same error message below.
> 
> * * *
> 
> In auth-source-backend-parse:
> gnus/auth-source.el:523:7:Warning: Obsolete name arg "Empty" to constructor
>     auth-source-backend
> * * * 
> 
> In auth-source-search-backends:
> gnus/auth-source.el:786:34:Warning: Unknown slot `:type'
> gnus/auth-source.el:787:15:Warning: Unknown slot `:source'
>   ELC      gnus/canlock.elc
>   ELC      gnus/compface.elc
>   ELC      gnus/deuglify.elc
> utf7.el: `mm-with-unibyte-current-buffer' is an obsolete macro (as of 25.1).
> mml2015.el: `mm-with-unibyte-current-buffer' is an obsolete macro (as of 25.1).
> mml2015.el: `mm-with-unibyte-current-buffer' is an obsolete macro (as of 25.1).
> mml2015.el: `mm-with-unibyte-current-buffer' is an obsolete macro (as of 25.1).
> make[2]: *** [gnus/deuglify.elc] Error 3
> make[2]: Leaving directory `/c/docume~1/lawlist/desktop/emacs/lisp'
> make[2]: Entering directory `/c/docume~1/lawlist/desktop/emacs/lisp'
>   ELC      mh-e/mh-thread.elc
> No MH variant found on the system
> make[2]: *** [mh-e/mh-thread.elc] Error 3
> make[2]: Leaving directory `/c/docume~1/lawlist/desktop/emacs/lisp'
> make[2]: Entering directory `/c/docume~1/lawlist/desktop/emacs/lisp'
>   ELC      url/url.elc
> make[2]: *** [url/url.elc] Error 3
> make[2]: Leaving directory `/c/docume~1/lawlist/desktop/emacs/lisp'
> make[1]: *** [compile-main] Error 2
> make[1]: Leaving directory `/c/docume~1/lawlist/desktop/emacs/lisp'
> make: *** [lisp] Error 2

I'm guessing that "Error 3" means Emacs aborted.  If that problem
still exists, we will need the details, like running the compilation
command under GDB.

Thanks.





  reply	other threads:[~2015-10-01  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 [this message]
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
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=83y4fn9ioz.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).