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: Sun, 21 Aug 2016 23:33:00 -0000	[thread overview]
Message-ID: <f09a4d80-5271-4775-34ba-4b7e72ba86b0@cornell.edu> (raw)
In-Reply-To: <91f48fa5-db3a-959c-5cb3-20b8df3a2791@gmail.com>

On 8/21/2016 11:24 AM, Marco Atzeri wrote:
> On 20/08/2016 18:54, Ken Brown wrote:
>> On 8/20/2016 9:41 AM, Marco Atzeri wrote:
>>> 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,
>>>
>
>>>
>>> It seems more a libgd3 build problem.
>>> Specially if it happens only on 32bit and not on 64bit.
>>
>> The difference between 32-bit and 64-bit is due to differences in
>> ImageMagick on the two platforms.
>>
>> On 32-bit, as I showed in an earlier message, I get:
>>
>> $ objdump -p /usr/bin/cygMagickCore-6.Q16-2.dll
>> [...]
>>         DLL Name: cyggd-3.dll
>>         vma:  Hint/Ord Member-Name Bound-To
>>         48ee2c      8  WebPDecode
>> [...]
>>
>> On 64-bit, I get:
>>
>> $ objdump -p /usr/bin/cygMagickCore-6.Q16-2.dll
>> [...]
>>         DLL Name: cygwebp-5.dll
>>         vma:  Hint/Ord Member-Name Bound-To
>> [...]
>>         48096c    271  WebPDecode
>> [...]
>>
>> Moreover, libMagickCore6_2 depends on libgd3 on 32-bit but not 64-bit.
>> So it seems that ImageMagick needs to be rebuilt on 32-bit so as to
>> remove this dependency.
>>
>> Ken
>>
>
> Hi Ken,
> the 32bit depends on both
>
> /usr/bin/cyggd-3.dll  =>  libgd3-2.1.1-2
> /usr/bin/cygwebp-5.dll  =>  libwebp5-0.4.4-1
>
> the 64 bit is missing  the first.
> So in theory I should rebuild the 64 one to include the libgd3
> dependency.
>
> You can verify with
> objdump -x  cygMagickCore-6.Q16-2.dll|grep DLL |sort
>
> The libgd3-2.1.1-2 has on both 32 and 64 bit
>
>  $ objdump -x cyggd-3.dll |grep WebP
>         [   8] WebPDecode
>         [   9] WebPEncode
>         [  10] WebPGetInfo
>         [  11] WebPGetPSNR
>
> So before my rebuild we need to understand what's happened to
> libgd3.

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.

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-21 22:03 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 [this message]
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=f09a4d80-5271-4775-34ba-4b7e72ba86b0@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).