From: David Edelsohn <dje.gcc@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Torvald Riegel <triegel@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH v2] libstdc++: Make certain exceptions transaction_safe.
Date: Sat, 16 Jan 2016 12:47:00 -0000 [thread overview]
Message-ID: <CAGWvnynBY3Zh+43Heu0Wkea5P3164XV=09+QOKqUUBGgREGR4Q@mail.gmail.com> (raw)
In-Reply-To: <20160116124323.GM15084@redhat.com>
stage1 libstdc++ builds just fine. the problem is stage2 configure
fails due to missing ITM_xxx symbols when configure tries to compile
and run conftest programs.
Thanks, David
On Sat, Jan 16, 2016 at 7:43 AM, Jonathan Wakely <jwakely@redhat.com> wrote:
> What are the errors?
>
> I can build libstdc++ on gcc111.
>
> Does this patch help?
>
>
next prev parent reply other threads:[~2016-01-16 12:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 12:16 David Edelsohn
2016-01-16 12:43 ` Jonathan Wakely
2016-01-16 12:47 ` David Edelsohn [this message]
2016-01-16 13:35 ` Jakub Jelinek
2016-01-16 13:41 ` Jonathan Wakely
2016-01-16 13:51 ` Jonathan Wakely
2016-01-16 20:12 ` Torvald Riegel
2016-01-16 20:24 ` David Edelsohn
2016-01-16 20:38 ` David Edelsohn
2016-01-17 20:21 ` Torvald Riegel
2016-01-17 20:32 ` Jakub Jelinek
2016-01-17 23:30 ` David Edelsohn
2016-01-18 13:54 ` Torvald Riegel
2016-01-18 16:30 ` Torvald Riegel
2016-01-18 20:08 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2016-01-16 9:57 Dominique d'Humières
2016-01-16 20:05 ` Torvald Riegel
2016-01-19 19:10 ` Torvald Riegel
2016-01-19 19:20 ` Jonathan Wakely
2016-01-21 10:00 ` Dominique d'Humières
2016-01-21 14:00 ` Torvald Riegel
2016-01-21 15:25 ` Torvald Riegel
2016-01-21 17:15 ` Dominique d'Humières
2016-01-21 17:29 ` Dominique d'Humières
2016-01-21 18:09 ` Mike Stump
2016-01-21 18:12 ` Pedro Alves
2016-01-21 18:18 ` Torvald Riegel
2016-01-07 16:47 Torvald Riegel
2016-01-14 17:58 ` Jonathan Wakely
2016-01-15 22:44 ` Torvald Riegel
2016-01-16 22:58 ` H.J. Lu
2016-01-17 16:59 ` Jonathan Wakely
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='CAGWvnynBY3Zh+43Heu0Wkea5P3164XV=09+QOKqUUBGgREGR4Q@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=triegel@redhat.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).