From: Rasmus Villemoes <rv@rasmusvillemoes.dk>
To: Olivier Hainque <hainque@adacore.com>
Cc: gcc-patches@gcc.gnu.org, Doug Rupp <rupp@adacore.com>
Subject: Re: [PATCH] gcc: vxworks: fix providing stdint.h header
Date: Fri, 19 Nov 2021 21:47:48 +0100 [thread overview]
Message-ID: <59882a60-816a-bb8e-8afe-a52b65a2fb86@rasmusvillemoes.dk> (raw)
In-Reply-To: <320A45E1-2E6C-416D-8088-2E30605AD570@adacore.com>
On 19/11/2021 19.11, Olivier Hainque wrote:
> Hi Rasmus,
>
>> On 12 Nov 2021, at 17:35, Olivier Hainque <hainque@adacore.com> wrote:
>
> Your error triggers on O2ggnu++0x.gch and we configure with
> --disable-libstdcxx-pch.
>
> Can you see if adding this to your configuration options helps
> on your end?
ISTR I already tried that, but just for good measure I did it again, and
no luck:
/bin/sh ../libtool --tag CXX --tag disable-shared --mode=compile
.../gcc-build/./gcc/xgcc -shared-libgcc -B.../gcc-build/./gcc
-nostdinc++ -L.../gcc-build/powerpc-wrs-vxworks/libstdc++-v3/src
-L.../gcc-build/powerpc-wrs-vxworks/libstdc++-v3/src/.libs
-L.../gcc-build/powerpc-wrs-vxworks/libstdc++-v3/libsupc++/.libs
-B/usr/powerpc-wrs-vxworks/bin/ -B/usr/powerpc-wrs-vxworks/lib/ -isystem
/usr/powerpc-wrs-vxworks/include -isystem
/usr/powerpc-wrs-vxworks/sys-include
--sysroot=/usr/powerpc-wrs-vxworks/sys-root
-fdebug-prefix-map=.../gcc-build/= -fdebug-prefix-map=.../gcc-src/=
-I.../gcc-src/libstdc++-v3/../libgcc
-I.../gcc-build/powerpc-wrs-vxworks/libstdc++-v3/include/powerpc-wrs-vxworks
-I.../gcc-build/powerpc-wrs-vxworks/libstdc++-v3/include
-I.../gcc-src/libstdc++-v3/libsupc++ -fno-implicit-templates -Wall
-Wextra -Wwrite-strings -Wcast-qual -Wabi=2
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections
-frandom-seed=del_opant.lo -g -O2 -mstrict-align -mmultiple
-fvisibility=hidden -c -o del_opant.lo
.../gcc-src/libstdc++-v3/libsupc++/del_opant.cc
.../gcc-src/libstdc++-v3/libsupc++/new_opa.cc:28:10: fatal error:
stdint.h: No such file or directory
28 | #include <stdint.h>
| ^~~~~~~~~~
compilation terminated.
Rasmus
next prev parent reply other threads:[~2021-11-19 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 10:15 Rasmus Villemoes
2021-11-12 16:35 ` Olivier Hainque
2021-11-19 18:11 ` Olivier Hainque
2021-11-19 20:47 ` Rasmus Villemoes [this message]
2021-11-20 8:07 ` Olivier Hainque
2021-12-02 15:29 ` Olivier Hainque
2021-12-03 10:27 ` Rasmus Villemoes
2021-12-03 11:40 ` Olivier Hainque
2021-12-06 3:05 ` Alexandre Oliva
2021-12-07 12:22 ` Olivier Hainque
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=59882a60-816a-bb8e-8afe-a52b65a2fb86@rasmusvillemoes.dk \
--to=rv@rasmusvillemoes.dk \
--cc=gcc-patches@gcc.gnu.org \
--cc=hainque@adacore.com \
--cc=rupp@adacore.com \
/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).