From: Zopolis0 <creatorsmithmdt@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Multiple descriptions for fassert in gcc/d/lang.opt and gcc/java/lang.opt
Date: Tue, 29 Mar 2022 19:11:23 +1100 [thread overview]
Message-ID: <CAEYL+X8Qo-zNW69+Kh5X_Yip7=KLvAwoQKx0SMMko8B4jVP0Dg@mail.gmail.com> (raw)
While trying to compile gcc with gcj re-added, it breaks on there being
multiple declarations of fassert in gcc/d/lang.opt and gcc/java/lang.opt.
options.cc:3241:2: error: #error Multiple different help strings for
fassert:
3241 | #error Multiple different help strings for fassert:
| ^~~~~
options.cc:3242:2: error: ‘Generate’ was not declared in this scope
3242 | Generate code for assert contracts.
| ^~~~~~~~
options.cc:3242:11: error: expected ‘}’ before ‘code’
3242 | Generate code for assert contracts.
Given that both of these definitions seem to be necessary, how do I resolve
this conflict?
gcc/java/lang.opt
fassert
Java Var(flag_assert) Init(1)
Permit the use of the assert keyword.gcc/d/lang.opt
fassert
D Var(flag_assert)
Generate code for assert contracts.
next reply other threads:[~2022-03-29 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 8:11 Zopolis0 [this message]
2022-03-29 15:41 ` Xi Ruoyao
2022-03-30 9:32 ` Zopolis0
2022-03-30 12:00 ` Segher Boessenkool
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='CAEYL+X8Qo-zNW69+Kh5X_Yip7=KLvAwoQKx0SMMko8B4jVP0Dg@mail.gmail.com' \
--to=creatorsmithmdt@gmail.com \
--cc=gcc-help@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).