1 |
Does anyone have any ideas on this one? If not, I'm going to file a bug |
2 |
report. |
3 |
|
4 |
--David |
5 |
|
6 |
|
7 |
On Tue, 2002-04-16 at 08:43, David Shepard wrote: |
8 |
> Hello All, |
9 |
> |
10 |
> As the subject says, something is definitely wrong. Here is what I have |
11 |
> done so far... After the thread on recompiling everything, I set out to |
12 |
> rebuild my system from the ground up, using gcc 3.0.4. After booting, I |
13 |
> compiled the compiler (with the 1.0-gcc3 profile). I then bootstrapped |
14 |
> the system, and then compiled the base system. So far so good, |
15 |
> everything went smoothly. Then I tried to compile something larger, |
16 |
> kde3. Everything was going fine, it compiled all the dependencies, |
17 |
> etc... But when it got to packages such as kdeutils and kdemultimedia, |
18 |
> it would send the compiler into what I could only describe as a loop |
19 |
> that just caused the disk to thrash, consuming more and more memory as |
20 |
> it went (over 100MB just for gcc). So life goes on, I don't really need |
21 |
> kde anyhow. I compiled evolution next and a few other small packages. |
22 |
> Besides the little libpng thing, everything was going fine. And then I |
23 |
> tried to get some actual work done and compile some of my own code... It |
24 |
> was really quite a simple piece of c++ code with no compiler |
25 |
> optimizations at all, just straight g++ foo.cpp -o foo. The compiler |
26 |
> produced some really weird error messages about 'using namespace std;', |
27 |
> yet not using that directive would tell me that I hadn't declared |
28 |
> 'cout'. Strange huh? End result, I had to ssh to a box that had gcc |
29 |
> 2.95.x on it to get some work done.(My code compiled without a hitch |
30 |
> there.) |
31 |
> |
32 |
> To make this long story short, are there any known problems with gcc |
33 |
> 3.0.4 before I go off filing a bug report? One last thing, I compiled |
34 |
> gcc with the basic optimizations that were provided: i686-pc-linux-gnu, |
35 |
> -march=i686 -03 -pipe. |
36 |
> |
37 |
> Anyone else had a similar problem/ ideas on how I can fix this? This |
38 |
> machine is pretty damn solid, so I believe I can rule out |
39 |
> memory/hardware failure. |
40 |
> |
41 |
> --David |
42 |
> |
43 |
> _______________________________________________ |
44 |
> gentoo-dev mailing list |
45 |
> gentoo-dev@g.o |
46 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |