From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: strange ezwinports issue
Date: Thu, 10 Sep 2015 19:48:21 +0300 [thread overview]
Message-ID: <834mj25iga.fsf@gnu.org> (raw)
In-Reply-To: <8737ym1cse.fsf@gmail.com>
> From: Sivaram Neelakantan <nsivaram.net@gmail.com>
> Date: Thu, 10 Sep 2015 21:34:17 +0530
>
> > There was no change that necessitated this. What this experiment
> > means is that you have a small "DLL hell" on your hands: you have an
> > incompatible copy of some DLL that is used by some of the ezwinports
> > that lives in some other directory which is closer to the beginning of
> > your PATH than the ezwinports' bin/ directory. So when Emacs loads,
> > say, libgnutls-28.dll, and looks for its dependency DLLs, it finds
> > that incompatible DLL first, tries to load it, which fails (due to
> > whatever makes it incompatible), and then the load of libgnutls-28.dll
> > fails because of that.
> >
>
> Right but this is a bit confusing. You see, the version that I was
> using earlier had all the DLLs under ezwinports and NOT under the
> Emacs bin directory. I renamed it as ezwinportsold and the downloaded
> one as ezwinports. At this point it stopped working. If I rename the
> old one back as ezwinports again, it works.
>
> Why does this work then?
Probably because the previous DLLs didn't depend on that incompatible
DLL which gives you trouble now.
prev parent reply other threads:[~2015-09-10 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 17:38 strange ezwinports issue Sivaram Neelakantan
2015-09-07 18:58 ` Eli Zaretskii
2015-09-08 3:02 ` Sivaram Neelakantan
2015-09-08 4:38 ` Eli Zaretskii
2015-09-10 16:04 ` Sivaram Neelakantan
2015-09-10 16:48 ` Eli Zaretskii [this message]
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=834mj25iga.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).