On Thu, 25 Oct 2007, mahesh mahesh wrote:
> But mpicc is available in correct path and added also,
And make detect that
> also; I think.
> Lots of objects files are created in mpi-unix directory
during compilation .
>
> Note this part
>
> ../render.c:108: error: static declaration of 'maxclr'
follows non-static
> declaration
> ../render.h:62: error: previous declaration of 'maxclr'
was here
> make[1]: *** [render.o] Error 1
> make[1]: Leaving directory
`/usr/local/povray31/source/mpi-unix'
> make: [newxwin] Error 2 (ignored)
>
> "mpicc: No such file or directory " is this
mesg from mpicc ??
>
> But which file is missing ???
> No information regarding this question int compilation
output !!!
The "No such file or directory" is coming from
mpicc, and is a bad error
message -- it can safely be ignored. When the underlying
compiler that
mpicc invokes fails (as it did in this case), mpicc
sometimes gets
confused and throws out a bad error message.
As Jeff said, the other error messages are the importat ones
-- if you fix
them so that the code compiles correctly, the mpicc error
will go away.
This looks like a simple static / non-static declaration /
definition
mismatch -- should be pretty easy to fix.
Good luck,
Brian
_______________________________________________
This list is archived at http://www.l
am-mpi.org/MailArchives/lam/
|
