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

20050803: LDM 6.4.1 compile problem on Solaris using gcc 3.4

>From: "Magee, David" <address@hidden>
>Organization: Navy
>Keywords: 200508032032.j73KW4jo024589 LDM 6.4.1 compile

Hi David,

Our LDM developer is on travel at the moment, so I will attempt to
help you past the compilation problem you are seeing.

re:
>I'm trying to compile ldm 6.4.1 on a Sun Ultra 10 running Solaris 9
>with GCC 3.4 
>
>I get an error during the "make"
>
>make[2]: Entering directory `/export/home/ldm/ldm-6.4.1/src/pqcheck'
>gcc -c -O -DNDEBUG  -I.. -I../config -I../misc -I../ulog -I../protocol
>-I../pq pqcheck.c
>pqcheck.c: In function `main':
>pqcheck.c:174: error: `LOG_locAl0' undeclared (first use in this function)
>pqcheck.c:174: error: (Each undeclared identifier is reported only once
>pqcheck.c:174: error: for each function it appears in.)
>make[2]: *** [pqcheck.o] Error 1
>make[2]: Leaving directory `/export/home/ldm/ldm-6.4.1/src/pqcheck'
>make[1]: *** [subdir_target] Error 1
>make[1]: Leaving directory `/export/home/ldm/ldm-6.4.1/src'
>make: *** [pqcheck/all] Error 2
>
>I'm stumped - can you help please?
>I've attached the log files

Your configure.log output indicates that c89, the compiler that
the build wants to use, was not found:

checking for c89... no
checking for cc... no
checking for gcc... gcc

I just built 6.4.1 on a Fedora Core 3 Linux machine where c89 is
an executable Bourne shell script:

more /usr/bin/c89
#!/bin/sh
fl="-std=c89"
for opt; do
  case "$opt" in
    -ansi|-std=c89|-std=iso9899:1990) fl="";;
    -std=*) echo "`basename $0` called with non ANSI/ISO C option $opt" >&2
            exit 1;;
  esac
done
exec /usr/bin/gcc $fl ${1+"$@"}

So, at least on FC Linux, the LDM build procedure wants "-std=c89"
defined.  Given this hint, I would recommend defining CFLAGS to
this value and rerunning the configure/make steps:

<as 'ldm'>
CFLAGS="-std=c89"
cd ~/ldm-6.4.1/src
./configure
make

Please let me know the results of this test.

Cheers,

Tom Yoksas
--
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.