From: Keith Seitz <keiths@redhat.com>
To: Sefer Tov <sefer@hotmail.com>
Cc: Jan Murawski <der@oelgoetze.de>,
"insight@sourceware.org" <insight@sourceware.org>
Subject: Re: Building problem
Date: Wed, 27 Mar 2013 05:26:00 -0000 [thread overview]
Message-ID: <515282FA.4000800@redhat.com> (raw)
In-Reply-To: <BAY002-W10523A8D01D4489A80368B4A8D10@phx.gbl>
On 03/26/2013 10:15 PM, Sefer Tov wrote:
> Thanks for the reply. I was actually trying to build the CVS HEAD version.
I built that this afternoon for x86_64-linux without incident.
> Seems like parts of the GDB code just won't compile with GCC 4.6
> complaining about C++ adherence problems (parts of the simulator) and
> after repeatedly patching them I eventually had to give up. I assume
> that an older compiler (maybe GCC 3.4 or 4.3) would accept that code
> however it's harder to get them built for a dual-arch (x86/x64) environment.
Over the past few days, there has been quite a bit of brokenness in the
simulators. Developers are working to sort it out. See, for example:
http://sourceware.org/ml/gdb-patches/2013-03/msg00871.html
[This is not the only thread on it; just the one I remember reading
about the most over the past week.]
Does your problem sound anything like that? [It doesn't really, but
without actual log of the build, it is unwise to commit. :-)]
> Have you tried building the CVS HEAD with newer GCC? I wonder if you'd
> be encountering the same issues.
I'm using gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC). This is
the Fedora 15 system compiler.
Keith
prev parent reply other threads:[~2013-03-27 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 0:47 Jan Murawski
2013-03-27 4:24 ` Keith Seitz
[not found] ` <BAY002-W10523A8D01D4489A80368B4A8D10@phx.gbl>
2013-03-27 5:26 ` Keith Seitz [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=515282FA.4000800@redhat.com \
--to=keiths@redhat.com \
--cc=der@oelgoetze.de \
--cc=insight@sourceware.org \
--cc=sefer@hotmail.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).