Can't attach a full log atm (for some reason I can't sftp from Windows to
Slack - but I'll fix this shortly). For some reason, when the error
occurred, the last few lines were not dumped into the file, so here they
are:
root_at_Chappell:/home/rob/lam-7.0.6# make > error.log
g++: Internal error: Killed (program cc1plus)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [laminfo.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1
root_at_Chappell:/home/rob/lam-7.0.6# dir error.log
To answer your question it's g++ 3.3.4. How do I tell if it's run out of
memory?
Cheers
Rob
----- Original Message -----
From: "Jeff Squyres" <jsquyres_at_[hidden]>
To: "General LAM/MPI mailing list" <lam_at_[hidden]>
Sent: Saturday, September 18, 2004 1:35 PM
Subject: Re: LAM: 7.0.6 install: "g++ internal error"
> On Sep 18, 2004, at 7:52 AM, Rob Malpass wrote:
>
>> I'm receiving an "g++ internal error" during compilation (the make stage)
>> of 7.0.6 from source. Installing binaries is not an option because I'm
>> using slackware.
>>
>> The install works fine on a PII-64Mb box but, even with an identical
>> configuration, is failing on a PI-150 with 32Mb RAM. I can't think of a
>> solution apart from cross-compilation.
>
> I have a dim recollection of seeing these kinds of things with older
> versions of g++, but can't find any old posts about it. :-\
>
> What version of g++ are you using? What program is it failing to compile?
> Can you tell if g++ is running out of memory when compiling?
>
> --
> {+} Jeff Squyres
> {+} jsquyres_at_[hidden]
> {+} http://www.lam-mpi.org/
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
