From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Zopolis0 <creatorsmithmdt@gmail.com>
Cc: Xi Ruoyao <xry111@xry111.site>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Segfault in libjava/prims.cc while compiling gcj
Date: Wed, 18 May 2022 11:43:06 +0100 [thread overview]
Message-ID: <CAH6eHdTfb3c38JRqcx27PdXY9OBYW9aRFy=QkTUOh4CZjUkbqw@mail.gmail.com> (raw)
In-Reply-To: <CAEYL+X9ruU+=NebkpNtjZ+Dg7bLtBCk5bntk4dJgqDx24jiw8w@mail.gmail.com>
On Wed, 18 May 2022 at 11:39, Zopolis0 via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> I'm unable to use the system g++ to compile it as removing any of the
> includes breaks it, removing any of the -B arguments breaks it, but not
> removing the -B arguments break it.
Don't remove them then, that's not what you were asked to do.
> Not exactly sure how to compile a
> preprocessed file either.
Rea the email you replied to, you use -E as described.
> As it stands, I have been unable to reproduce the
> error or change any of the flags, although I have been able to produce a
> preprocessed file as per your instructions.
Because you didn't follow the instructions.
next prev parent reply other threads:[~2022-05-18 10:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 9:23 Zopolis0
2022-05-18 9:59 ` Xi Ruoyao
2022-05-18 10:38 ` Zopolis0
2022-05-18 10:43 ` Jonathan Wakely [this message]
2022-05-18 10:45 ` Zopolis0
2022-05-18 10:57 ` Jonathan Wakely
2022-05-18 11:01 ` Xi Ruoyao
2022-05-18 23:20 ` Zopolis0
2022-05-19 4:32 ` Zopolis0
2022-05-19 8:06 ` Xi Ruoyao
2022-05-20 10:50 ` Zopolis0
2022-05-18 11:16 ` Zopolis0
2022-05-19 10:47 ` Florian Weimer
2022-05-19 12:22 ` Zopolis0
2022-05-21 7:12 ` Zopolis0
2022-06-15 7:51 ` Zopolis0
2022-06-17 9:20 ` Zopolis0
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='CAH6eHdTfb3c38JRqcx27PdXY9OBYW9aRFy=QkTUOh4CZjUkbqw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=creatorsmithmdt@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=xry111@xry111.site \
/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).