1 |
Check USE/C flags, there may have been changes between versions (I think this happened to me) Try compiling without any of them and if it works start looking for the bad one. |
2 |
|
3 |
W.Kenworthy |
4 |
|
5 |
|
6 |
On 01/02/2012, at 5:37, walt <w41ter@×××××.com> wrote: |
7 |
|
8 |
> On 01/31/2012 11:57 AM, Grant wrote: |
9 |
>> I can't seem to get gcc-4.5.3-r1 to compile. I tried twice and it |
10 |
>> failed at the exact same point both times. The build log doesn't |
11 |
>> mention a segfault. Does anyone know how to fix this? I was able to |
12 |
>> compile gcc-4.3.3 a short while ago. |
13 |
> |
14 |
> Are you using the new 4.3.3 to build 4.5.3? The gcc package actually |
15 |
> compiles gcc twice, once with your existing compiler and again with |
16 |
> the new compiler itself (at least it worked that way in the old days). |
17 |
> |
18 |
> I'm wondering if the internal compiler error occurs during the first |
19 |
> build (using 4.3.3) or the second (using 4.5.3). |
20 |
> |
21 |
> Not that I'd know what to do with that info except to answer my own |
22 |
> question :) |
23 |
> |
24 |
> |