public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: emacs-w32 not starting - libgd3 problem
Date: Mon, 22 Aug 2016 13:23:00 -0000	[thread overview]
Message-ID: <da9a040a-6006-df30-5609-da7bcd8baa7c@cornell.edu> (raw)
In-Reply-To: <4bc25f38-bb68-00fc-cefe-2ead210ff3c8@gmail.com>

On 8/22/2016 3:17 AM, Peter Hull wrote:
> On 21/08/16 23:03, Ken Brown wrote:
>> OK, let's wait to hear from Volker (or maybe Yaakov has some insight?).
>>
>> BTW, I've looked at the sources for gd-2.2.3-1, and the string
>> "WebPDecode" appears only once, in a call to WebPDecodeARGB.  So I
>> don't understand why there wasn't an ABI bump between versions 2.1.1
>> and 2.2.3.
>
> Thanks very much everyone for looking into this issue. In the interim,
> is there a way for me to get emacs running again by using cygwin setup
> to install an earlier version of ImageMagick (or gd?)

Install the previous version (2.1.1-2) of libgd3.

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2016-08-22 12:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 13:55 emacs-w32 not starting - missing dependency? Peter Hull
2016-08-19 14:17 ` Ken Brown
2016-08-19 18:59   ` Ken Brown
2016-08-19 20:43     ` Ken Brown
2016-08-19 21:54       ` Ken Brown
2016-08-20 13:27       ` Ken Brown
2016-08-20 16:03         ` Marco Atzeri
2016-08-20 21:12           ` Ken Brown
2016-08-21 21:36             ` emacs-w32 not starting - libgd3 problem Marco Atzeri
2016-08-21 23:33               ` Ken Brown
2016-08-22  8:00                 ` Yaakov Selkowitz
2016-08-22  9:57                 ` Peter Hull
2016-08-22 13:23                   ` Ken Brown [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

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

  git send-email \
    --in-reply-to=da9a040a-6006-df30-5609-da7bcd8baa7c@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.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.
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).