From: Nick Clifton <nickc@redhat.com>
To: sebastien@milkymist.org
Cc: gcc-patches@gcc.gnu.org
Subject: RFA: LM32: Configure with newlib-stdint.h
Date: Tue, 06 Oct 2015 13:36:00 -0000 [thread overview]
Message-ID: <877fn0uniw.fsf@redhat.com> (raw)
Hi Sebastien,
I recently found that I could not build libstdc++ for the lm32-elf
target because the port lacked a definition of __INTPTR_TYPE__. I
tracked this down to the fact that INTPTR_TYPE was not being defined
when building gcc, and this in turn was due to the fact that the
newlib stdint types were not being defined. So please may I apply the
patch below to correct this problem ?
Cheers
Nick
gcc/ChangeLog
2015-10-06 Nick Clifton <nickc@redhat.com>
* config.gcc (lm32-elf): Add newlib-stdint.h to tm_file.
Index: gcc/config.gcc
===================================================================
--- gcc/config.gcc (revision 228513)
+++ gcc/config.gcc (working copy)
@@ -1834,7 +1834,7 @@
md_file=iq2000/iq2000.md
;;
lm32-*-elf*)
- tm_file="dbxelf.h elfos.h ${tm_file}"
+ tm_file="dbxelf.h elfos.h ${tm_file} newlib-stdint.h"
tmake_file="${tmake_file} lm32/t-lm32"
;;
lm32-*-rtems*)
next reply other threads:[~2015-10-06 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 13:36 Nick Clifton [this message]
2015-10-06 21:06 ` Jeff Law
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=877fn0uniw.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sebastien@milkymist.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).