From: LIU Hao <lh_mouse@126.com>
To: Eric Botcazou <botcazou@adacore.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC trunk bootstrap failure on i686-w64-mingw32
Date: Sat, 29 Oct 2022 20:20:44 +0800 [thread overview]
Message-ID: <b3b67ec0-af02-6822-2426-85c0f4a75f07@126.com> (raw)
In-Reply-To: <3462286.iIbC2pHGDl@fomalhaut>
[-- Attachment #1.1: Type: text/plain, Size: 292 bytes --]
在 2022-10-29 20:15, Eric Botcazou 写道:
>> So what could be causing it?
>
> An oversight in https://gcc.gnu.org/pipermail/gcc-cvs/2022-August/370830.html
> has broken --disable-sjlj-exceptions. That's now fixed.
>
Thank you. Rebuilding now.
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2022-10-29 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 10:52 LIU Hao
2022-10-29 12:15 ` Eric Botcazou
2022-10-29 12:20 ` LIU Hao [this message]
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=b3b67ec0-af02-6822-2426-85c0f4a75f07@126.com \
--to=lh_mouse@126.com \
--cc=botcazou@adacore.com \
--cc=gcc@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).