all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: emacs-devel@gnu.org
Subject: Re: gnutls on mingw64
Date: Wed, 27 Nov 2019 17:53:40 +0200	[thread overview]
Message-ID: <83blsxqprv.fsf@gnu.org> (raw)
In-Reply-To: <86zhghod06.fsf@stephe-leake.org> (message from Stephen Leake on Wed, 27 Nov 2019 02:00:09 -0800)

> From: Stephen Leake <stephen_leake@stephe-leake.org>
> Date: Wed, 27 Nov 2019 02:00:09 -0800
> 
> >> Currently neither w32_delayed_load nor init_gnutls_functions calls
> >> GetLastError; would it help to add that?
> >
> > Does its value tell something useful in this case?
> 
> I did not modify the code to find out, but I'm guessing it's the
> standard unhelpful "could not find the file" without the file name.

But it did find the file, it just couldn't load it because some of its
dependencies were of incorrect architecture/ABI.

IMO, it only makes sense to call GetLastError and display the results
to the user if the message will allow the user figure out what went
wrong and how to fix it.



  reply	other threads:[~2019-11-27 15:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 12:34 gnutls on mingw64 Stephen Leake
2019-11-26 15:42 ` Richard Copley
2019-11-27  1:10   ` Stephen Leake
2019-11-27  8:56     ` Richard Copley
2019-11-27  9:58       ` Stephen Leake
2019-11-26 15:46 ` Eli Zaretskii
2019-11-27 10:00   ` Stephen Leake
2019-11-27 15:53     ` Eli Zaretskii [this message]
2019-11-28 18:00       ` Stephen Leake
2019-11-28 22:22         ` Richard Copley
2019-11-29  7:17           ` Eli Zaretskii
2019-11-29  8:32             ` Richard Copley
2019-11-29 10:24               ` Eli Zaretskii
2019-11-29  3:16         ` Juanma Barranquero

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=83blsxqprv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.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.