From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 3d1678: Make creation of ld.so.conf optional
Date: Wed, 22 Mar 2017 18:56:00 -0000 [thread overview]
Message-ID: <58d2c8e966a79_5a013f7fed237c2c1307bf@hookshot-fe6-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 3d1678a7f65ae541eba7114fe7447c38c7d9259d
https://github.com/crosstool-ng/crosstool-ng/commit/3d1678a7f65ae541eba7114fe7447c38c7d9259d
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-22 (Wed, 22 Mar 2017)
Changed paths:
M config/libc.in
M scripts/build/internals.sh
Log Message:
-----------
Make creation of ld.so.conf optional
... enabled by default for multilib and disabled otherwise. Buildroot
has been complaining about /etc/ld.so.conf presence for almost a year
now and I missed that.
After the release, xldd will be modified to query the compiler for
the list of multilibs to search. This would be too invasive change
before 1.23, though.
Note that it may lead to configurations where xldd currently does not
find the libraries (if both DEMULTILIB and CREATE_LDSO_CONF are turned
off). This is not the default setting in Kconfig, though.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 54f43778b1a2723481f3df304b67ead45fe91862
https://github.com/crosstool-ng/crosstool-ng/commit/54f43778b1a2723481f3df304b67ead45fe91862
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-22 (Wed, 22 Mar 2017)
Changed paths:
M config/libc.in
M scripts/build/internals.sh
Log Message:
-----------
Merge pull request #657 from stilor/no-ldsoconf
Make creation of ld.so.conf optional
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/91169535d707...54f43778b1a2
reply other threads:[~2017-03-22 18:56 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=58d2c8e966a79_5a013f7fed237c2c1307bf@hookshot-fe6-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).