It looks like you're not grabbing both stdout and stderr.
tcsh: make >&! make.out
sh: make 2>&1 > make.out
This does look like a gcc bug, but I can't say for sure. LAM uses
fairly basic C++ stuff -- nothing too fancy. It looks like you're
dying while building the "laminfo" executable. In a worst case
scenario, laminfo is not required for correct LAM functionality (aside
from mpiexec). You could "make -k" and skip the laminfo executable --
but you'll need to ensure that no other errors occur, as well.
Note that LAM only has 4 C++ executables:
- laminfo
- mpicc
- mpic++
- mpif77
We used C++ for these programs because they do lots of string
manipulation, and std::string is just sooo much nicer than (char*). So
if you skip laminfo, no problem. But you'll probably need mpicc (etc.)
-- if you get a compiler error there, too, it's looking more like a
compiler bug.
Did you find anything looking in gcc's bugzilla or Slack's error
tracking?
On Sep 18, 2004, at 10:18 AM, Rob Malpass wrote:
> 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/
>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
