From: Bryan Hundven <bryanhundven@gmail.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 75dee8: Fix issue #449.
Date: Tue, 04 Oct 2016 18:21:00 -0000 [thread overview]
Message-ID: <57f3f326137fd_75823f836fd7d14c121831@hookshot-fe4-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 75dee86653f7ca23aac7fcc89c1982a65c6a5c36
https://github.com/crosstool-ng/crosstool-ng/commit/75dee86653f7ca23aac7fcc89c1982a65c6a5c36
Author: Alexey Neyman <stilor@att.net>
Date: 2016-10-02 (Sun, 02 Oct 2016)
Changed paths:
M scripts/build/cc/100-gcc.sh
Log Message:
-----------
Fix issue #449.
After building final gcc, place the libraries in non-sysroot libs
into sysroot.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 96338beecacca6c416cf88558367c61089c8d959
https://github.com/crosstool-ng/crosstool-ng/commit/96338beecacca6c416cf88558367c61089c8d959
Author: Alexey Neyman <stilor@att.net>
Date: 2016-10-02 (Sun, 02 Oct 2016)
Changed paths:
M scripts/build/cc/100-gcc.sh
Log Message:
-----------
GCC uses multi_os_dir for libgcc, not multi_dir.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 62e136d46d1f1164116dbf0732ef94f9db95fec1
https://github.com/crosstool-ng/crosstool-ng/commit/62e136d46d1f1164116dbf0732ef94f9db95fec1
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-10-04 (Tue, 04 Oct 2016)
Changed paths:
M scripts/build/cc/100-gcc.sh
Log Message:
-----------
Merge pull request #459 from stilor/static-libgcc-link
Fix issue #449.
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/531eab4c5650...62e136d46d1f
[-- Attachment #2: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2016-10-04 18:21 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=57f3f326137fd_75823f836fd7d14c121831@hookshot-fe4-cp1-prd.iad.github.net.mail \
--to=bryanhundven@gmail.com \
--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).