From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 3dbb57: Make companion libs static.
Date: Fri, 16 Dec 2016 20:53:00 -0000 [thread overview]
Message-ID: <585454287c400_57853f7f73cdb13054651@hookshot-fe3-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 2660 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 3dbb576c1708c1683ef780a43dec31a220458f39
https://github.com/crosstool-ng/crosstool-ng/commit/3dbb576c1708c1683ef780a43dec31a220458f39
Author: Alexey Neyman <stilor@att.net>
Date: 2016-12-11 (Sun, 11 Dec 2016)
Changed paths:
A samples/x86_64-w64-mingw32,arm-cortexa9_neon-linux-gnueabihf/crosstool.config
A samples/x86_64-w64-mingw32,arm-cortexa9_neon-linux-gnueabihf/reported.by
M scripts/build/companion_libs/200-libelf.sh
M scripts/build/companion_libs/210-expat.sh
M scripts/build/companion_libs/220-ncurses.sh
M scripts/build/companion_libs/320-libiconv.sh
M scripts/build/companion_libs/330-gettext.sh
Log Message:
-----------
Make companion libs static.
This follows the trend set by 1*.sh scripts that configure ISL, GMP,
MPFR, CLooG, etc. Building with shared libraries presents all kinds
of problems:
- The shared libraries need to be installed into ${CT_PREFIX_DIR}.
- The binaries linked against companion libs need to have proper
RPATH, or they're looking for shared libs in
.build/${CT_PREFIX}/buildtools/lib.
- All libraries must agree as to whether they're built shared,
static, or both. Otherwise, gettext tries to link in static libncurses.a
into a shared library and fails (since libncurses was compiled without
the -fPIC switch and hence contains relocations that cannot be handled
in a shared library).
So this fixes the current mess. If we decide to re-enable building
the companion libs shared, we should probably make this dependent on
a separate suboption of CT_STATIC_TOOLCHAIN.
Add a config loosely based on one reported in the issue 274.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 400f9e097265e66113cb46fb8f903af4e491f306
https://github.com/crosstool-ng/crosstool-ng/commit/400f9e097265e66113cb46fb8f903af4e491f306
Author: Alexey Neyman <stilor@att.net>
Date: 2016-12-16 (Fri, 16 Dec 2016)
Changed paths:
A samples/x86_64-w64-mingw32,arm-cortexa9_neon-linux-gnueabihf/crosstool.config
A samples/x86_64-w64-mingw32,arm-cortexa9_neon-linux-gnueabihf/reported.by
M scripts/build/companion_libs/200-libelf.sh
M scripts/build/companion_libs/210-expat.sh
M scripts/build/companion_libs/220-ncurses.sh
M scripts/build/companion_libs/320-libiconv.sh
M scripts/build/companion_libs/330-gettext.sh
Log Message:
-----------
Merge pull request #506 from stilor/canadian-gettext-mingw32
Make companion libs static; fix gettext build on mingw
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/7bea082b3ff7...400f9e097265
reply other threads:[~2016-12-16 20:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=585454287c400_57853f7f73cdb13054651@hookshot-fe3-cp1-prd.iad.github.net.mail \
--to=stilor@att.net \
--cc=crossgcc@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).