X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:subject:from:to:date:in-reply-to
	:references:content-type:mime-version:content-transfer-encoding;
	 q=dns; s=default; b=IAq5X7USUrmb+1p1aQ7S7kWdwNpL1X+GR+Br+0HWpjb
	gVCH1CyKZ4WauX1jvdkelssy7jHGWkGE8kjD87H+C4jFtcZwUf7XQ3MrvWxMrYs1
	kKG2TcjzqCvbzV3e+mYAnNuvfqbTULGHotnGO3FXKwTNTphvzrkw8sH2wp/NIISU
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:subject:from:to:date:in-reply-to
	:references:content-type:mime-version:content-transfer-encoding;
	 s=default; bh=4fABGCxrKSglu2V6CC6SKWYarSw=; b=nshSjrsTE6nnfli4i
	Wyw7AVFvAcGbFhpzm3+UDkgFHJXH2EMXFNXqbU8oReV0bdXGXygISarSVU8uE3SO
	jidiueKI/QIplXwlem6mdyEG29B+edrs43RXinkxJxjMYjGfLxLZ+x0rbbu9Xf5D
	oouWOqUUXlA3UP/qT6r7rbj6xo=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=H*M:cygwin, AFAICS, afaics, mistakenly
X-HELO: mx1.redhat.com
Message-ID: <1471836479.3047.10.camel@cygwin.com>
Subject: Re: emacs-w32 not starting - libgd3 problem
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Date: Sun, 21 Aug 2016 23:27:59 -0400
In-Reply-To: <f09a4d80-5271-4775-34ba-4b7e72ba86b0@cornell.edu>
References: <966a14c2-ee69-7d3d-800e-a4f9f62a3ec9@gmail.com>	 <b3b9e712-32d1-59ca-d549-9b461865a6a6@cornell.edu>	 <f9f0713e-b151-6716-e5ee-6225716d595e@cornell.edu>	 <dc6c9caf-5227-c64f-8c67-6b3b9c5c85e8@cornell.edu>	 <69ab42c7-0c3b-e8ce-978f-77c52b8c1a56@cornell.edu>	 <b23dbc5b-aa2e-7757-6a77-30524ee9d8d1@gmail.com>	 <6c85acfc-dec8-e215-8519-94884190b198@cornell.edu>	 <91f48fa5-db3a-959c-5cb3-20b8df3a2791@gmail.com>	 <f09a4d80-5271-4775-34ba-4b7e72ba86b0@cornell.edu>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Note-from-DJ: This may be spam

On Sun, 2016-08-21 at 18:03 -0400, Ken Brown wrote:
> On 8/21/2016 11:24 AM, Marco Atzeri wrote:
> > 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?).

AFAICS ImageMagick should be rebuilt, and the result should be a
dependency on libwebp5 and not libgd3.

> 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.

That's because it was supposed to be an internal symbol which was only
mistakenly exposed for linking (unfortunately we don't have ELF
visibility support).  Some background:

https://github.com/libgd/libgd/issues/129
https://github.com/libgd/libgd/commit/a79232c5fa692c3b6e3f5bc95ecfc4554
24c3f54
https://github.com/libgd/libgd/commit/824a3aaa37b422779166ccc0ffc17e777
f8cf291

--
Yaakov


--
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

