[Met_help] Fwd: compiling METv1.1

[John Halley Gotway]

Nilza,

Looks like you missed a step when building BUFRLIB.  BUFRLIB consists of
FORTRAN source code as well as C source code.  But with your commands, you
only compiled the FORTRAN source code.  Please try the following:

gcc -c -DUNDERSCORE *.c
g77 -c -DUNDERSCORE -fno-second-underscore *.f
ar crv libbufr.a *.o

This is taken from a page of the MET Online Tutorial:
http://www.dtcenter.org/met/users/support/online_tutorial/compilation/req_libs.php

Thanks,

John

> Dear John,
>
> Thanks a lot for you help. Your suggestion solve my  problem.
> But now the chief difficulty I found was while I am trying to compile the
> METV1.1. As you can
> see the problem is related to BUFRLIB.
>
> I've attached  make_met.log and my Makefile.
>
> I hope you can help me!!
>
> Best Regards
>
>
>
>
> ====below the way I built the BUFRLIB===
> g77 -c -DUNDERSCORE -fno-second-underscore *.f
> ar crv libbufr.a *.o
> =======
>
> I  pasted the nm comander below. Since I read something about that in the
> Met_help
>
> ======
>
>
>
> kurumin at dpn_kurumin:~/BUFRLIB$ nm ~/BUFRLIB/libbufr.a | grep bort
>          U bort_
> bort2.o:
> 00000000 T bort2_
>          U bort_exit_
> bort.o:
> 00000000 T bort_
>          U bort_exit_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort2_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort2_
>          U bort2_
>          U bort_
>          U bort2_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort2_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort2_
>          U bort_
>          U bort_
>          U bort_
>          U bort2_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort2_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort2_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort2_
>          U bort_
>          U bort_
>          U bort_
>          U bort2_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort2_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
>          U bort_
> =========================
>
>
> On Mon, Dec 15, 2008 at 5:30 PM, John Halley Gotway
> <johnhg at rap.ucar.edu>wrote:
>
>> Nilza,
>>
>> I took a look at your "make_met.log" file.  Thanks for sending that.
>>
>> I've never actually encountered compiler error messages in languages
>> other
>> than English... but I'm guessing that the phrase...
>> "Arquivo ou diretório não encontrado"
>> ... translates to...
>> "File or directory no found"
>>
>> Is that correct?  It looks like your build of the GNU Scientific Library
>> may not have fully succeeded.
>>
>> Does the file "/home/kurumin/gsl-1.9/include/gsl/gsl_cdf.h" exist on
>> your
>> machine?  If not, you'll need to look at the installation of GSL.
>>
>> You can try re-building GSL with the following commands:
>> cd /home/kurumin/gsl-1.9
>> make clean
>> ./configure --prefix=/home/kurumin/gsl-1.9
>> make
>> make install
>>
>> After you've rebuilt it, look to see if the file
>> "/home/kurumin/gsl-1.9/include/gsl/gsl_cdf.h" exists now.  If so, try
>> rebuilding MET.
>>
>> Thanks and good luck,
>> John Halley Gotway
>>
>> Nilza BARROS wrote:
>> > Sorry, I have forget ted  the files. Now I sending it.
>> >
>> > Thanks
>> > Nilza Barros
>> > ---------- Forwarded message ----------
>> > From: Nilza BARROS <nilzabarros at gmail.com>
>> > Date: Sun, Dec 14, 2008 at 8:35 PM
>> > Subject: Fwd: compiling METv1.1
>> > To: met_help at ucar.edu
>> >
>> >
>> > Dear Sir,
>> >
>> > I am really interested in the MET but unfortunately I found some
>> problems
>> in
>> > compiling it.
>> >
>> > I have attached  my Makefile and make_met.log.
>> >
>> > I have compiled BUFRLIB, netCDF 1.6 ,gls1.9 and I am using the  lf2c
>> and
>> > lg2c that was installed with apt-get install in Debian.
>> >
>> > I really appreciate any help.
>> >
>> >
>> > Best Regards,
>> >
>> > Nilza Barros
>> >
>> >
>> >
>> >
>> >
>> > ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > Met_help mailing list
>> > Met_help at mailman.ucar.edu
>> > http://mailman.ucar.edu/mailman/listinfo/met_help
>>
>
>
>
> --
> Abraço,
> Nilza Barros
>