From: Eli Zaretskii <eliz@gnu.org>
To: binutils@sourceware.org
Subject: Binutils 2.27 linked statically to libintl
Date: Sun, 21 Aug 2016 10:40:00 -0000 [thread overview]
Message-ID: <834m6ecsmh.fsf@gnu.org> (raw)
Hi,
I built Binutils 2.27 natively on MS-Windows, using mingw.org's MinGW
tools, and found that the programs are linked statically to libintl
and libiconv, which makes the binaries significantly more fat.
Binutils 2.26, built on the same machine, was linked dynamically to
those libraries.
Digging a little deeper, I see that intl/config.intl says in Binutils
2.27:
USE_NLS='yes'
LIBINTL='d:/usr/lib/libintl.a d:/usr/lib/libiconv.a'
LIBINTL_DEP=''
INCINTL=''
whereas in 2.26 it said this:
USE_NLS='yes'
LIBINTL='-lintl'
LIBINTL_DEP=''
INCINTL=''
The same 'configure' command was used in both cases.
Can someone tell what am I doing wrong, and how can I cause the build
to use the dynamic link to shared libraries? Is it a bug that I
should report to the Binutils Bugzilla?
TIA
P.S. I'm not subscribed to this list, so please CC me on the
responses.
next reply other threads:[~2016-08-21 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 10:40 Eli Zaretskii [this message]
2016-08-23 9:21 ` Nick Clifton
2016-08-23 14:31 ` Eli Zaretskii
2016-08-25 15:06 ` Eli Zaretskii
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=834m6ecsmh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=binutils@sourceware.org \
/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).