On Fri, 21 May 2004, Andy Young wrote:
> I am confused about what to do with this make error. It says that a
> macro has been already defined. I have attached the output to this
> message, as well as the script that I put the configure flags into
> (setuplam.s.)
A tip for you with tcsh -- note that your script continued despite the
fact that "make" failed.
You might want to change it a little to be:
/wrk2/andy/lam-7.0.4/configure ....all the configure args... \
>& lamsetups.txt && \
make >>& lamsetups.txt && \
make install >>& lamsetups.txt
Then "make" and "make install" will only run if the previous steps
succeeded. Indeed, you can actually combine the two "make" steps by "make
all install".
Just a friendly tip...
> This error is different than the one I was having earlier, which was
> caused by an AIX xlc6.0 compiler failure under heavy optimization.
This appears to be beacause we're defining the same macro twice. This
actually doesn't cause a problem in any other compiler -- we're defining
it to be the same value in both places (it's a long, complicated story).
So in a central config header file (lam_config.h) we're #defining LAM_CC
to be "xlc". Then, we're #defining it again it
lam-ssi-boot-globus-config.h (to be the same value). This will actually
happen in all the SSI subdirectories; disabling the globus module won't
help.
Is there an xlc command line parameter that can disable this error?
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
