LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Andy Young (andy314159pi_at_[hidden])
Date: 2004-05-24 15:19:39


Hi Jeff,
Thanks for answering my post again Jeff. I looked
through the xlc compiler manual, but I could not find
a compiler option that will disable the behavior of
allowing only one macro definition. I do not know how
to program in C (I use fortran,) so it really is
possible that I overlooked something. It seems like
the options that you can give to the preprocessor are
quite limited. Most of the options you can pass to
xlc are for compiling options. So I am sort of at a
loss. Well maybe I'll look over than manual again and
see if I missed anything.
-Andy Young
JHU chemistry

 
--- Jeff Squyres <jsquyres_at_[hidden]> wrote:
> 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/
> _______________________________________________
> This list is archived at
http://www.lam-mpi.org/MailArchives/lam/

        
                
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/