From: Daniel Colascione <dancol@dancol.org>
To: cygwin-apps@cygwin.com
Subject: Re: libgif depends on X11
Date: Mon, 15 Oct 2012 09:58:00 -0000 [thread overview]
Message-ID: <507BDE3E.3020707@dancol.org> (raw)
In-Reply-To: <20121015082128.GC2110@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]
On 10/15/2012 1:21 AM, Corinna Vinschen wrote:
> On Oct 14 18:45, Daniel Colascione wrote:
>> $ ldd /bin/cyggif-4.dll
>> ntdll.dll => /Windows/SysWOW64/ntdll.dll (0x7de70000)
>> kernel32.dll => /Windows/syswow64/kernel32.dll (0x7dd60000)
>> KERNELBASE.dll => /Windows/syswow64/KERNELBASE.dll (0x7d850000)
>> cyggcc_s-1.dll => /usr/bin/cyggcc_s-1.dll (0xc3c70000)
>> cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
>> cygX11-6.dll => /usr/bin/cygX11-6.dll (0xc4e90000)
>> cygxcb-1.dll => /usr/bin/cygxcb-1.dll (0xc02f0000)
>> cygXau-6.dll => /usr/bin/cygXau-6.dll (0xc4e70000)
>> cygXdmcp-6.dll => /usr/bin/cygXdmcp-6.dll (0xc4dd0000)
>> ??? => ??? (0x580000)
>>
>> Why would libgif depend on X11? The symbols imported are XGetImage,
>> XGetWindowAttributes, and XQueryColors.
>
> Same as on Linux:
>
> $ ldd /lib64/libgif.so.4
> linux-vdso.so.1 => (0x00007fffffbff000)
> libSM.so.6 => /lib64/libSM.so.6 (0x0000003fbdc00000)
> libICE.so.6 => /lib64/libICE.so.6 (0x0000003fbe000000)
> libX11.so.6 => /lib64/libX11.so.6 (0x0000003fb3800000)
> libc.so.6 => /lib64/libc.so.6 (0x0000003faf800000)
> libuuid.so.1 => /lib64/libuuid.so.1 (0x0000003fb9c00000)
> libxcb.so.1 => /lib64/libxcb.so.1 (0x0000003fb3c00000)
> libdl.so.2 => /lib64/libdl.so.2 (0x0000003fb0400000)
> /lib64/ld-linux-x86-64.so.2 (0x0000003faf400000)
> libXau.so.6 => /lib64/libXau.so.6 (0x0000003fb3400000)
>
Not on Debian stable at least:
$ ldd /usr/lib/libgif.so.4.1
linux-gate.so.1 => (0xf7791000)
libc.so.6 => /lib/i686/cmov/libc.so.6 (0xf763a000)
/lib/ld-linux.so.2 (0xf7792000)
According to NEWS, giflib gained a configure option for disabling X11 support in
4.1.5. The X dependency in giflib appears to be there for capturing an X window
as a GIF file. I somehow doubt this functionality would be missed.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
prev parent reply other threads:[~2012-10-15 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 1:45 Daniel Colascione
2012-10-15 8:22 ` Corinna Vinschen
2012-10-15 9:58 ` Daniel Colascione [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=507BDE3E.3020707@dancol.org \
--to=dancol@dancol.org \
--cc=cygwin-apps@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).