From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: emacs-w32 not starting - missing dependency?
Date: Sat, 20 Aug 2016 16:03:00 -0000 [thread overview]
Message-ID: <b23dbc5b-aa2e-7757-6a77-30524ee9d8d1@gmail.com> (raw)
In-Reply-To: <69ab42c7-0c3b-e8ce-978f-77c52b8c1a56@cornell.edu>
On 20/08/2016 04:52, Ken Brown wrote:
> On 8/19/2016 4:03 PM, Ken Brown wrote:
>> On 8/19/2016 11:22 AM, Ken Brown wrote:
>>> On 8/19/2016 9:55 AM, Ken Brown wrote:
>>>> On 8/19/2016 6:27 AM, Peter Hull wrote:
>>>>> Hi all,
>> The problem turns out to be related to the recent update of libgd3.
>> Reverting to the previous version fixes it.
>>
>> Notice that cygMagickCore-6.Q16-2.dll, which occurs in the error dialog
>> above, depends on cyggd-3.dll:
>>
>> $ cygcheck /usr/bin/cygMagickCore-6.Q16-2.dll | grep cyggd-3
>> C:\cygwin\bin\cyggd-3.dll
>>
>> Marco, is it possible that the libgd3 update requires a rebuild of
>> ImageMagick?
>
> Or maybe the issue is that the latest build of gd should have had an ABI
> bump. Volker?
>
> Ken
>
It seems more a libgd3 build problem.
Specially if it happens only on 32bit and not on 64bit.
The removal of an interface requires a ABI bump at upstream level,
but that it will happen for both arch versions.
Regards
Marco
--
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
next prev parent reply other threads:[~2016-08-20 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 13:55 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 [this message]
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
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=b23dbc5b-aa2e-7757-6a77-30524ee9d8d1@gmail.com \
--to=marco.atzeri@gmail.com \
--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).