From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 16d166: Force wide char support in uClibc if GDB8 is enabl...
Date: Thu, 08 Jun 2017 22:06:00 -0000 [thread overview]
Message-ID: <5938fd57d282c_e6e3fd63d617c38109965@hookshot-fe2-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 16d166c2c87a232fae40f8613d43a08fe8cbdc90
https://github.com/crosstool-ng/crosstool-ng/commit/16d166c2c87a232fae40f8613d43a08fe8cbdc90
Author: Alexey Neyman <stilor@att.net>
Date: 2017-06-08 (Thu, 08 Jun 2017)
Changed paths:
M config/debug/gdb.in.gdbserver
M config/debug/gdb.in.native
Log Message:
-----------
Force wide char support in uClibc if GDB8 is enabled
GDB8 (or rather gnulib that is a part of it) provides a fallback mbstate_t
definition - but GCC's C++ headers (which are used via stdint.h since GDB8
uses C++) provide another mbstate_t if libc does not have wide char support.
These two definitions conflict with each other.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 29ecbf84c86098423a7228765aa9324c931eecc8
https://github.com/crosstool-ng/crosstool-ng/commit/29ecbf84c86098423a7228765aa9324c931eecc8
Author: Alexey Neyman <stilor@att.net>
Date: 2017-06-08 (Thu, 08 Jun 2017)
Changed paths:
M config/debug/gdb.in.gdbserver
M config/debug/gdb.in.native
Log Message:
-----------
Merge pull request #739 from stilor/sh4-gdb-uclibc
Force wide char support in uClibc if GDB8 is enabled
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/10089f3c9aa4...29ecbf84c860
reply other threads:[~2017-06-08 7:31 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=5938fd57d282c_e6e3fd63d617c38109965@hookshot-fe2-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).