From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 6af04d: cross-gdb: account for canadian/crossnative toolch...
Date: Thu, 30 Mar 2017 06:13:00 -0000 [thread overview]
Message-ID: <58dca1f6357c5_1ab43ffc251ddc2c2368f@hookshot-fe5-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 6af04d822bdcd533ce731ba245f50bfbc22ed4a4
https://github.com/crosstool-ng/crosstool-ng/commit/6af04d822bdcd533ce731ba245f50bfbc22ed4a4
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-29 (Wed, 29 Mar 2017)
Changed paths:
M config/cc/gcc.in.2
M config/debug/gdb.in.cross
M config/toolchain.in
M scripts/crosstool-NG.sh.in
Log Message:
-----------
cross-gdb: account for canadian/crossnative toolchains
... when determining if it can be linked statically, and if Python
scripting should default to y.
Prompted by a failure of i686-w64-mingw32,nios2-spico-elf sample
on a system where configure didn't report static linking support.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: a7edff1820d89b45449c7764644fbfa3562e3297
https://github.com/crosstool-ng/crosstool-ng/commit/a7edff1820d89b45449c7764644fbfa3562e3297
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-29 (Wed, 29 Mar 2017)
Changed paths:
M config/cc/gcc.in.2
M config/debug/gdb.in.cross
M config/toolchain.in
M scripts/crosstool-NG.sh.in
Log Message:
-----------
Merge pull request #667 from stilor/cross-gdb-deps
cross-gdb: account for canadian/crossnative toolchains
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/54a4975220e6...a7edff1820d8
reply other threads:[~2017-03-30 6:13 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=58dca1f6357c5_1ab43ffc251ddc2c2368f@hookshot-fe5-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).