public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: why python3 depends on libintl-devel ?
Date: Tue, 31 Oct 2017 23:59:00 -0000	[thread overview]
Message-ID: <56b38fb9-722a-aedd-130a-cab4c9ce336a@cygwin.com> (raw)
In-Reply-To: <fe9111dc-1a94-57ab-9f86-2f117b67c89d@wanadoo.fr>


[-- Attachment #1.1: Type: text/plain, Size: 907 bytes --]

On 2017-10-31 16:10, Jérôme Bouat wrote:
> I noticed that the python3 package depends on the libintl-devel package.

Only indirectly.

> Why python3 depends on a development package ?

ctypes.util.find_library()[1] uses dlltool from binutils to derive the
name of the DLL from the given import library name.  This might sound
odd, but on ELF platforms gcc is also a requirement, as a small program
is compiled and linked just in order to figure out the SONAME of a given
library name.

The binutils package includes both the programs and the (static) libbfd,
libiberty, and libopcodes libraries; it is for those that libintl-devel
is a dependency of binutils.  Perhaps we could consider splitting out
these libraries and their headers into a separate package
(libbfd-devel?) to avoid this.

[1] https://docs.python.org/3.6/library/ctypes.html#finding-shared-libraries

-- 
Yaakov


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2017-10-31 23:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 21:10 Jérôme Bouat
2017-10-31 23:59 ` Yaakov Selkowitz [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=56b38fb9-722a-aedd-130a-cab4c9ce336a@cygwin.com \
    --to=yselkowitz@cygwin.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).