From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] a596ec: Fix up the sysroot issue for sh4 in a different wa...
Date: Mon, 27 Mar 2017 17:08:00 -0000 [thread overview]
Message-ID: <58d946ee6064d_5d5a3fb757051c2c651e5@hookshot-fe3-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: a596ec5b39f900b1f4b481cc46afd20b0e5457d2
https://github.com/crosstool-ng/crosstool-ng/commit/a596ec5b39f900b1f4b481cc46afd20b0e5457d2
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-26 (Sun, 26 Mar 2017)
Changed paths:
M samples/sh4-multilib-linux-gnu/crosstool.config
M samples/sh4-multilib-linux-uclibc/crosstool.config
M scripts/build/arch.sh
M scripts/build/arch/sh.sh
M scripts/build/cc/100-gcc.sh
M scripts/crosstool-NG.sh.in
Log Message:
-----------
Fix up the sysroot issue for sh4 in a different way
(see the comments in the code for details on the issue)
Old workaround in 100-gcc.sh stopped working (probably, due to one
of GCC version upgrades), so switch to the other approach originally
described there: adjust the list of multilibs to not include the
default target explicitly.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 32909ec654abcc281a513b769879271b120ddf6f
https://github.com/crosstool-ng/crosstool-ng/commit/32909ec654abcc281a513b769879271b120ddf6f
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-27 (Mon, 27 Mar 2017)
Changed paths:
M samples/sh4-multilib-linux-gnu/crosstool.config
M samples/sh4-multilib-linux-uclibc/crosstool.config
M scripts/build/arch.sh
M scripts/build/arch/sh.sh
M scripts/build/cc/100-gcc.sh
M scripts/crosstool-NG.sh.in
Log Message:
-----------
Merge pull request #662 from stilor/sh-multilib
Fix up the sysroot issue for sh4 in a different way
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/de1366132956...32909ec654ab
reply other threads:[~2017-03-27 17:08 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=58d946ee6064d_5d5a3fb757051c2c651e5@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).