From: David Shepard <dshepard@wvu.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Something is wrong with my compiler
Date: 16 Apr 2002 16:42:09 +0000 [thread overview]
Message-ID: <1018975330.2074.0.camel@davetop> (raw)
In-Reply-To: <1018946608.2098.2.camel@davetop>
Does anyone have any ideas on this one? If not, I'm going to file a bug
report.
--David
On Tue, 2002-04-16 at 08:43, David Shepard wrote:
> Hello All,
>
> As the subject says, something is definitely wrong. Here is what I have
> done so far... After the thread on recompiling everything, I set out to
> rebuild my system from the ground up, using gcc 3.0.4. After booting, I
> compiled the compiler (with the 1.0-gcc3 profile). I then bootstrapped
> the system, and then compiled the base system. So far so good,
> everything went smoothly. Then I tried to compile something larger,
> kde3. Everything was going fine, it compiled all the dependencies,
> etc... But when it got to packages such as kdeutils and kdemultimedia,
> it would send the compiler into what I could only describe as a loop
> that just caused the disk to thrash, consuming more and more memory as
> it went (over 100MB just for gcc). So life goes on, I don't really need
> kde anyhow. I compiled evolution next and a few other small packages.
> Besides the little libpng thing, everything was going fine. And then I
> tried to get some actual work done and compile some of my own code... It
> was really quite a simple piece of c++ code with no compiler
> optimizations at all, just straight g++ foo.cpp -o foo. The compiler
> produced some really weird error messages about 'using namespace std;',
> yet not using that directive would tell me that I hadn't declared
> 'cout'. Strange huh? End result, I had to ssh to a box that had gcc
> 2.95.x on it to get some work done.(My code compiled without a hitch
> there.)
>
> To make this long story short, are there any known problems with gcc
> 3.0.4 before I go off filing a bug report? One last thing, I compiled
> gcc with the basic optimizations that were provided: i686-pc-linux-gnu,
> -march=i686 -03 -pipe.
>
> Anyone else had a similar problem/ ideas on how I can fix this? This
> machine is pretty damn solid, so I believe I can rule out
> memory/hardware failure.
>
> --David
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-04-16 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 8:43 [gentoo-dev] Something is wrong with my compiler David Shepard
2002-04-16 16:42 ` David Shepard [this message]
2002-04-16 20:41 ` Thilo Bangert
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=1018975330.2074.0.camel@davetop \
--to=dshepard@wvu.edu \
--cc=gentoo-dev@gentoo.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