[Met_help] MET installation problem

[John Halley Gotway]

Litta,

I noticed something right away in the information you sent...  It looks like you're using the wrong compilers.

xlc is a C compiler, and xlC is a C++ compiler.  It's pretty annoying that the only difference is the lower-case vs upper-case letter 'c', but that's the difference between them.  And you should be
using the C++ compiler here.

Try setting:
CXX = /usr/vac/bin/xlC
FC  = /usr/vac/bin/xlf

And then be sure to do a "/path/to/your/make clean" before trying to rebuild.  That should help a lot.

Thanks,
John

Litta A J wrote:
> Dear sir,
> 
>  Thank you very much for your kind information...  You are right. It is
> making libraries after typing as you specified.. It is successfully creating
> vx_afm Library, vx_analysis_util Library, vx_cal Library files. But it is
> not creating vx_color library. I am attaching make.log file and the
> specified lines of stdlib.h Please go through that and give your valuable
> suggestion.... My CXX path is  as follows...
> 
> # Path to the C++ Compiler
> # C++ compiler flags
> # Any additional required libraries
> CXX          = /usr/vac/bin/xlc
> CXX_FLAGS    = # -g -qfullpath
> CXX_LIBS     =
> 
> thunder>/user2/litta/MET_T/make-3.81/make
> *** Making the Model Evaluation Tools Project ***
> 
> *** Making vx_afm Library ***
> /usr/vac/bin/cc afm.cc   -c -I..
> /usr/vac/bin/cc afm_keywords.cc   -c -I..
> /usr/vac/bin/cc afm_line.cc   -c -I..
> /usr/vac/bin/cc afm_token.cc   -c -I..
> /usr/vac/bin/cc afmkeyword_to_string.cc   -c -I..
> /usr/vac/bin/cc afmtokentype_to_string.cc   -c -I..
> ar -rs libvx_afm.a afm.o afm_keywords.o afm_line.o afm_token.o
> afmkeyword_to_string.o afmtokentype_to_string.o
> ar: Creating an archive file libvx_afm.a.
> ranlib libvx_afm.a
> cp libvx_afm.a ../.
> *** Making vx_analysis_util Library ***
> 
> *** Making vx_cal Library ***
> 
> *** Making vx_color Library ***
> /usr/vac/bin/cc vx_color.cc   -c -I..
> "/usr/vacpp/include/cstdlib", line 72.15: 1540-0403 (S) "abs(long)" is
> already defined.
> "/usr/vacpp/include/stdlib.h", line 146.32: 1540-0425 (I) "abs" is defined
> on line 146 of "/usr/vacpp/include/stdlib.h".
> "/usr/vacpp/include/stdlib.h", line 38.32: 1540-0424 (I) "abs" is declared
> on line 38 of "/usr/vacpp/include/stdlib.h".
> make[3]: *** [vx_color.o] Error 1
> make[2]: *** [vx_color_all] Error 2
> make[1]: *** [libs] Error 2
> make: *** [all] Error 2
> Looking forward to your reply..............
> 
> with best regards,
> Litta
> 
> 
> On Wed, Feb 17, 2010 at 8:52 PM, John Halley Gotway <johnhg at ucar.edu> wrote:
> 
>> Litta,
>>
>> I went to an IBM machine here and tried building MET using the *WRONG*
>> version of make, not the GNU make.  When I did that, I saw the exact same
>> error messages you're seeing.  Based on the command
>> line you sent me, it looks like you're just typing "make" on the command
>> line.  Doing that tells the shell to search your path for "make", and I'm
>> guessing it's still finding the wrong version of it -
>> and not the one that you installed in your home directory.  Instead, you'll
>> need to type something like this:
>>
>> thunder> cd METv2.0
>> thunder> /home/litta/path/to/make
>>
>> Where that path specifies the location of the GNU make executable you just
>> built.
>>
>> Let me know if you continue to experience problems.
>>
>> Thanks,
>> John
>>
>>
>>
>