Charm++ parallel programming system

[Jim Phillips <jim AT ks.uiuc.edu>]

FYI, xlC_r is just the thread-safe mode of xlC.  This may be the default 
now, or your path may just be missing something.  Check man xlC or 
/usr/vacpp/bin.

Jim


On Wed, 11 Dec 2013, Phil Miller wrote:

> On Wed, Dec 11, 2013 at 11:20 AM, Mengyuan Zhu 
> <mzhu6 AT student.gsu.edu>wrote:
>
> >  I can run xlc as it is in /usr/bin. But in that folder there is no xlC_r
> > and there are only xlc and xlc++. The administrator knows little about the
> > cluster and did not want to compile it. So I used gcc instead.
> In that case, you should be able to modify the variables in
> charm-6.4.0/src/arch/lap/cc-xlc.sh to refer to xlc and xlc++ instead of
> xlc_r and xlC_r. You may need to do the same to the NAMD 'arch' files that
> Jim mentioned as well.
>
>
> >  Best regards,
> >
> > Mengyuan Zhu
> >
> >
> >  ------------------------------
> > *From:* 
> > unmobile AT gmail.com
> >  
> > <unmobile AT gmail.com>
> >  on behalf of Phil Miller <
> > mille121 AT illinois.edu>
> > *Sent:* Wednesday, December 11, 2013 14:13
> > *To:* Mengyuan Zhu; Charm Mailing List
> >
> > *Subject:* Re: [charm] Charm compile in IBM AIX UNIX
> >
> >  On Wed, Dec 11, 2013 at 11:09 AM, Mengyuan Zhu 
> > <mzhu6 AT student.gsu.edu>wrote:
> >
> > >  Thank you!
> > >
> > > My command:
> > >  ./build charm++ lapi xlc        --with-production
> > >
> > > But there is problem with our unix:
> > >
> > > ../bin/charmc -host  xi-main.C
> > > ../bin/charmc[2]: xlC_r:  not found.
> > > Fatal Error by charmc in directory
> > > /rc/home/wang/mzhu6/bin/NAMD_2.9_Source/charm-6.4.0/lapi-xlc/tmp
> > >    Command xlC_r -q32 -D_H_UNISTD -DYY_NEVER_INTERACTIVE=1
> > > -I../bin/../include -D__CHARMC__=1 -c xi-main.C -o xi-main.o returned error
> > > code 127
> > > charmc exiting...
> >  Is your xlc installation's bin/ directory in your path? You can run
> > 'echo $PATH' to see.
> >
> >
> > >  Best regards,
> > >
> > > Mengyuan Zhu
> > >
> > >
> > >  ------------------------------
> > > *From:* 
> > > unmobile AT gmail.com
> > >  
> > > <unmobile AT gmail.com>
> > >  on behalf of Phil Miller
> > > <mille121 AT illinois.edu>
> > > *Sent:* Wednesday, December 11, 2013 13:51
> > > *To:* Mengyuan Zhu
> > > *Cc:* 
> > > charm AT cs.illinois.edu
> > > *Subject:* Re: [charm] Charm compile in IBM AIX UNIX
> > >
> > >    You could drop the 'gcc' and 'gfortran' options, and use the default
> > > xlC compiler toolchain. I believe that is expected to provide better
> > > performance on POWER hardware, though the NAMD developers would have to
> > > confirm that.
> > >
> > >  So that we can fully understand your situation, could you please
> > > describe what resources led you to choose the lapi-gcc-gfortran build
> > > target?
> > >
> > >
> > > On Wed, Dec 11, 2013 at 10:43 AM, Mengyuan Zhu 
> > > <mzhu6 AT student.gsu.edu>wrote:
> > >
> > > >  Dear,
> > > >
> > > > As I want to compile NAMD2.9 in AIX UNIX, I have to compile charm first.
> > > >
> > > > This is my command:
> > > > ./build charm++ lapi gcc   gfortran     --with-production
> > > >
> > > > This is my error:
> > > >
> > > > g++: error: unrecognized command line option '-qstrict'
> > > > Fatal Error by charmc in directory
> > > > /rc/home/wang/mzhu6/bin/NAMD_2.9_Source/charm-6.4.0/lapi-gfortran-gcc/tmp
> > > >    Command g++ -fPIC -Wno-deprecated -DCMK_GFORTRAN -I../bin/../include
> > > > -D__CHARMC__=1 -I. -O3 -qstrict -Q -c trace-common.C -o trace-common.o
> > > > returned error code 1
> > > > charmc exiting...
> > > >
> > > >
> > > >  What can I do?
> > > >
> > > >
> > > >  Best regards,
> > > >
> > > > Mengyuan Zhu
> > > >
> > > >
> > > > _______________________________________________
> > > > charm mailing list
> > > > charm AT cs.uiuc.edu
> > > > http://lists.cs.uiuc.edu/mailman/listinfo/charm