From: Albert Chin <gcc@mlists.thewrittenword.com>
To: gcc@gcc.gnu.org
Subject: Re: SEGV building qt-3.3.3 with GCC 3.4.3 on RH 7.1/RHEL 2.1
Date: Fri, 03 Dec 2004 17:13:00 -0000 [thread overview]
Message-ID: <20041203171347.GA32781@mail1.thewrittenword.com> (raw)
In-Reply-To: <20041202160806.A1814@synopsys.com>
On Thu, Dec 02, 2004 at 04:08:06PM -0800, Joe Buck wrote:
> On Thu, Dec 02, 2004 at 04:33:02PM -0600, Albert Chin wrote:
> > Just build Qt-3.3.3 with GCC 3.4.2 and 3.4.3 on Redhat Linux 7.1/x86
> > and RHEL 2.1/x86. No problems with 3.4.2. However, when building with
> > 3.4.3, I get a segfault during the build:
> > ...
> > Redhat Linux 9/x86, RHEL 3.0/x86, and RHEL 3.0/amd64 work fine. I
> > reviewed http://gcc.gnu.org/gcc-3.4/changes.html#3.4.3 but nothing
> > stands out as to what causes this. Where should I start looking?
>
> Are you saying that you get a segfault when you build with 3.4.3 on RHEL
> 2.1, but not when you build with 3.4.3 on RHEL 3.0 or RH9? If so, this
> doesn't sound like the compiler is at fault. A KDE developers' list might
> be a better place to track this one down, but I don't see any alternative
> to just debugging the problem. If the blowup is in a place where there
> appears to be no code, it's probably in a destructor.
Sorry, my fault. I incorrectly installed binutils-2.15 so gcc-3.4.3
never built against it.
--
albert chin (china@thewrittenword.com)
next prev parent reply other threads:[~2004-12-03 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 22:33 Albert Chin
2004-12-03 0:08 ` Joe Buck
2004-12-03 17:13 ` Albert Chin [this message]
2004-12-07 15:56 ` Nix
2004-12-09 20:46 ` Michael Matz
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=20041203171347.GA32781@mail1.thewrittenword.com \
--to=gcc@mlists.thewrittenword.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).