[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDD #YXF-596402]: VM for McIDAS at DU

Hi Matt,

> Building ldm-mcidas, I get the following after make:
> making `basic' in directory /usr/local/ldm/ldm-mcidas-2008/src/decode
> make[2]: Entering directory `/usr/local/ldm/ldm-mcidas-2008/src/decode'
> test -r udalloc.c || ln -s ../port/misc/udalloc.c udalloc.c
> c89 -c -O -I/usr/local/ldm/include -I/usr/local/mcidas/mcidas2009/src

Given my recommendations on setting environment variables before retrying
a build of ldm-mcidas, I am surprised to see 'c89'.  I have run into problems
before when the C compiler is set to c89 (unlike the LDM build which wants
one to use 'c89'), and the solution has always been to use 'cc' or 'gcc'.

Please retry using the following settings:

make distclean

setenv CC gcc
setenv CPPFLAGS "-DNDEBUG -Df2cFortran"
setenv CFLAGS -O
setenv FC gfortran
setenv FFLAGS "-O -Wuninitialized -fno-automatic"
setenv CPP_LDM -I/usr/local/ldm/include
setenv LD_LDM '-L/usr/local/ldm/lib -lldm'
setenv CPP_MCIDAS -I/home/mcidas/inc
setenv LD_MCIDAS '-L/home/mcidas/lib -lmcidas'
setenv CPP_NETCDF -I/home/mcidas/include
setenv LD_NETCDF '-L/home/mcidas/lib -lnetcdf'
setenv LD_MATH '-L/usr/lib -lm'

> -I/usr/local/include -I../libpng -I../port/misc -I../port/cfortran
> -I../zlib  alarm.c
> In file included from alarm.c:11:
> alarm.h:24: error: field âoldactâ has incomplete type
> alarm.h:25: error: field ânewactâ has incomplete type
> make[2]: *** [alarm.o] Error 1
> make[2]: Leaving directory `/usr/local/ldm/ldm-mcidas-2008/src/decode'
> make[1]: *** [decode/basic] Error 1
> make[1]: Leaving directory `/usr/local/ldm/ldm-mcidas-2008/src'
> + set +x

> I'd rather build from source than use the binary so I'm sure
> everything is linked properly;

I completely agree with this approach.  This is the main reason that
both the LDM and McIDAS are offered only as source.

> does this look like an obvious build error?

I think the error associated with 'alaram' will go away when 'c89'
is not used as the C compiler.


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: YXF-596402
Department: Support IDD
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.