Hi Dave, re: > Trying to get a test system set up and having issues getting the decoders > installed > > A) > wxt-idd:~/ldm-mcidas-2012/src> uname -a > Linux wxt-idd 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016 > x86_64 x86_64 x86_64 GNU/Linux > > B) > wxt-idd:~/ldm-mcidas-2012/src> cat VERSION > 2012 > > C) > wxt-idd:~/ldm-mcidas-2012/src> which gcc cc gfortran g++ > /usr/bin/gcc > /usr/bin/gfortran > /usr/bin/g++ > > wxt-idd:~/ldm-mcidas-2012/src> gcc --version > gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609 > Copyright (C) 2015 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > wxt-idd:~/ldm-mcidas-2012/src> gfortran --version > GNU Fortran (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609 > Copyright (C) 2015 Free Software Foundation, Inc. > > GNU Fortran comes with NO WARRANTY, to the extent permitted by law. > You may redistribute copies of GNU Fortran > under the terms of the GNU General Public License. > For more information about these matters, see the file named COPYING > > wxt-idd:~/ldm-mcidas-2012/src> g++ --version > g++ (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609 > Copyright (C) 2015 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > I have included a few more files than requested (i.e. packages, libraries, > etc) to help identify if there is any additional libraries that I somehow > missed. > > Any help would be appreciated. I have successfully built ldm-mcidas v2012 on my Lubuntu system (a single board Odroid U3) using the following environment variable settings before running 'configure': export CC=gcc export CFLAGS=-O export CPPFLAGS='-DNDEBUG -Df2cFortran' export FC=gfortran export FFLAGS='-O -Wuninitialized -fno-automatic' export CPP_LDM=-I/home/ldm/include export LD_LDM='/home/ldm/lib/libldm.a' export CPP_MCIDAS=-I/home/mcidas/inc export LD_MCIDAS='-L/home/mcidas/lib -lmcidas' export CPP_NETCDF=-I/home/mcidas/mcidas2016/netcdf/libsrc export LD_NETCDF='-L/home/mcidas/lib -lnetcdf' The biggest difference I see in my settings compared to yours is 'LD_LDM'. This is likely the area you need to concentrate given the error I see in the 'make.log' file you attached: cc -O -Wl,-rpath,DMHOME/lib -o area2png alarm.o commonsubs.o imgsubs.o pngsubs.o rtesubs.o area2png.o -LDMHOME/lib -lldm -lxml2 ../port/misc/libudport.a -L/home/mcidas/lib -lnetcdf -L../libpng -lpng -L../zlib -lz -lm || (rm -f area2png; exit 1) /usr/bin/ld: cannot find -lldm collect2: error: ld returned 1 exit status Makefile:852: recipe for target 'area2png' failed make[2]: *** [area2png] Error 1 make[2]: Leaving directory '/home/ldm/ldm-mcidas-2012/src/decode' Makefile:139: recipe for target 'decode/basic' failed make[1]: *** [decode/basic] Error 1 make[1]: Leaving directory '/home/ldm/ldm-mcidas-2012/src' + set +x The bit I am keying on is '/usr/bin/ld: cannot find -lldm'. The other thing that I think is important is to link against the static LDM library, not the shared one. This will keep you from having to monkey with LD_LIBRARY_PATH to have the ~ldm/lib directory searched. Please let me know if this helps! Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: PRB-573465 Department: Support ldm-mcidas Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.