From: Olivier Hainque <hainque@adacore.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [patch] Add include-fixed to include search paths for libgcc on VxWorks
Date: Thu, 24 Sep 2020 19:08:10 +0200 [thread overview]
Message-ID: <F594EA04-138D-418A-AB16-5888DD061ABC@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
The special vxworks rules for the compilation of libgcc had
-I.../gcc/include and not .../gcc/include-fixed, causing build
failure of our arm-vxworks7r2 port because of indirect dependencies
on limits.h.
The omission was just an oversight and this change just adds the
missing -I,
This fixes the aforementioned build failure, has been used in gcc-9
based production compilers for several targets for a year, passed a build
& test sequence for powerpc-vxworks7 with gcc-10 and a sanity check build
with a recent mainline.
Committing to mainline shortly.
Olivier
2020-09-24 Olivier Hainque <hainque@adacore.com>
libgcc/
* config/t-vxworks: Add include-fixed to include search
paths for libgcc on VxWorks.
* config/t-vxworks7: Likewise.
[-- Attachment #2: 0003-Add-include-fixed-to-include-search-paths-for-libgcc.diff --]
[-- Type: application/octet-stream, Size: 1117 bytes --]
diff --git a/libgcc/config/t-vxworks b/libgcc/config/t-vxworks
index 757cead6724..e1f1e937687 100644
--- a/libgcc/config/t-vxworks
+++ b/libgcc/config/t-vxworks
@@ -12,6 +12,7 @@ LIB2ADD += $(srcdir)/config/vxcache.c
# prevail (e.g. unwind.h), and that gcc provided header files intended
# to be user visible eventually are visible as well.
LIBGCC2_INCLUDES = -nostdinc -I. \
+ -I$(MULTIBUILDTOP)../../gcc/include-fixed \
-I$(MULTIBUILDTOP)../../gcc/include \
`case "/$(MULTIDIR)" in \
*/mrtp*) echo -I$(WIND_USR)/h -I$(WIND_USR)/h/wrn/coreip ;; \
diff --git a/libgcc/config/t-vxworks7 b/libgcc/config/t-vxworks7
index f2cc904ac08..75f6cb4a29f 100644
--- a/libgcc/config/t-vxworks7
+++ b/libgcc/config/t-vxworks7
@@ -12,6 +12,7 @@ LIB2ADD += $(srcdir)/config/vxcache.c
# prevail (e.g. unwind.h), and that gcc provided header files intended
# to be user visible eventually are visible as well.
LIBGCC2_INCLUDES = -nostdinc -I. \
+ -I$(MULTIBUILDTOP)../../gcc/include-fixed \
-I$(VSB_DIR)/h -I$(VSB_DIR)/share/h \
-I$(MULTIBUILDTOP)../../gcc/include \
`case "/$(MULTIDIR)" in \
--
2.17.1
[-- Attachment #3: Type: text/plain, Size: 2 bytes --]
reply other threads:[~2020-09-24 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=F594EA04-138D-418A-AB16-5888DD061ABC@adacore.com \
--to=hainque@adacore.com \
--cc=gcc-patches@gcc.gnu.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).