Compilation Error on 64 bit Fedora Core 3

[Colin McGuigan]

Tony Baylis wrote:
 > We are trying to upgrade our Mapserver app from 3.6.6 to the latest
on a new
 > 64 bit machine using Fedora Core 3.
 >
 > After trying to install from .src.rpm and encountering issues related to
 > 64bit, I have started again using .tar.gz files for all packages except
 > those that can be installed or updated using yum, ie devel packages etc.
 >
 > The following ./configure command was used and succeeded:
 >
 > ./configure --with-jpeg --with-php=/usr/include/php/main
 > --with-php-regex-dir=/usr/src/redhat/BUILD/php-4.3.10/build-cgi/regex
 > --with-gdal --with-png --with-wmsclient --with-libwww --without-tiff
 > --with-geos --with-postgis --with-freetype --enable-force-freetype1
 > --enable-runpath
 >
 > BUT compilation (make -d) fails giving the following final output:
 >
 >      Finished prerequisites of target file `maptemplate.o'.
 >     Must remake target `maptemplate.o'.
 > gcc -c -O2 -fPIC  -Wall -DIGNORE_MISSING_DATA -DNEED_STRLCAT  -DUSE_EPPL
 >    -DUSE_GD_GIF -DUSE_GD_PNG -DUSE_GD_JPEG -DUSE_GD_WBMP -DUSE_GD_FT
 > -DGD_HAS_GDIMAGEGIFPTR -DGD_HAS_GETBITMAPFONTS     -DUSE_GDAL -DUSE_GEOS
 > -DUSE_ICONV  -DUSE_PHP_REGEX
 > -I/usr/src/redhat/BUILD/php-4.3.10/build-cgi/regex/.. -DUSE_POSTGIS
 > -I/usr/include        -I/usr/local/include -I/usr/include     -I
 > maptemplate.c -o maptemplate.o
 > Putting child 0x00547bd0 (maptemplate.o) PID 5464 on the chain.
 > Live child 0x00547bd0 (maptemplate.o) PID 5464
 > gcc: no input files
 > Got a SIGCHLD; 1 unreaped children.
 > Reaping losing child 0x00547bd0 PID 5464
 > make: *** [maptemplate.o] Error 1
 > Removing child 0x00547bd0 PID 5464 from chain.

I would check your ./configure again.  Specifically, in the gcc compile
step, there should be something between the last "-I" and
"maptemplate.c".  As it is, gcc is thinking that maptemplate.c is to be
included, when it's really what should be compiled.

I ran into this when I tried --with-proj without specifying a directory
after.  You'd think the configure script would've noticed, but it
didn't.  So I would check ./configure --help to see which of those flags
requires a path, and then try setting them.

--Colin McGuigan