Re: [vox-tech] (Moved from [vox]) Errors in software compilation
On Wednesday 09 March 2005 11:00 pm, Bill Kendrick wrote: On Wed, Mar 09, 2005 at 05:58:40PM -0800, Mark K. Kim wrote: Where's your `./configure` step??? In Dylan's original post, he said the configure step worked fine, but that IS a good question. Dylan, can you start fresh and cut-n-paste the initial configure and make steps into an email here? Right I should have included it from the start. please see the configure output at the end of this email... here were the configure options; ./configure --prefix=/usr --with-png=internal --with-jpeg=internal \ --with-gif=internal --with-libtiff=internal \ --with-geotiff=internal --with-libz=internal\ --without-pg --without-ogdi --with-python \ --with-threads=yes Also, is this app downloadable from anywhere? (I don't remember if you had mentioned an URL in any prev posts) yes, from here: http://www.gdal.org/index.html Thanks for looking at this! -- Dylan Beaudette Soils and Biogeochemistry Graduate Group University of California at Davis 530.754.7341 checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/i486-slackware-linux/bin/ld checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes checking for /usr/i486-slackware-linux/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... g++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc static flag works... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/i486-slackware-linux/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag CXX to libtool checking for ld used by g++... /usr/i486-slackware-linux/bin/ld checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/i486-slackware-linux/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/i486-slackware-linux/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes appending configuration tag F77 to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for g77 option to produce PIC... -fPIC checking if g77 PIC flag -fPIC works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/i486-slackware-linux/bin/ld) supports shared libraries... yes checking dynamic linker
Re: [vox-tech] (Moved from [vox]) Errors in software compilation
On Wednesday 09 March 2005 03:28 pm, Bill Kendrick wrote:
Hi Dylan. This kind of question actually belongs over here on vox-tech,
so I've replied here, instead of plain 'vox'...
Thanks Bill!
On Wed, Mar 09, 2005 at 03:30:13PM -0800, Dylan Beaudette wrote:
Hi everyone,
I am using a software package called GDAL here at work, and it compiles
fine on my Debian Sarge box... However, the *same* source tree fails to
compile on a similar machine running Slackware...
snip
On your Sarge box, do you have cpl_port.h and/or cpl_error.h anywhere
else, besides the 'gdal' build directory?
Yes:
[EMAIL PROTECTED]:~$ locate cpl_port
/home/dylan/src/gdal-1.2.5/port/cpl_port.h
/usr/local/include/cpl_port.h
...However, the file didn't make it into /usr/include/ until after the make
install step...
After copying the GDAL-specific headers to /usr/include:
find . -name *.h -exec cp '{}' /usr/include/ \;
... make seems to be chugging along fine... but then there is what seems to be
an endless loop with:
-
.
make[965]: Entering directory `/home/dylan/src/gdal-1.2.5/frmts'
make[965]: Nothing to be done for `default'.
make[965]: Leaving directory `/home/dylan/src/gdal-1.2.5/frmts'
(cd ogr; make lib )
make[965]: Entering directory `/home/dylan/src/gdal-1.2.5/ogr'
make[965]: Nothing to be done for `lib'.
make[965]: Leaving directory `/home/dylan/src/gdal-1.2.5/ogr'
make
[ad infinitum]
and a CTRL-C results in:
---
...
make[11]: *** [check-lib] Interrupt
make[10]: *** [check-lib] Interrupt
make[9]: *** [check-lib] Interrupt
make[8]: *** [check-lib] Interrupt
make[7]: *** [check-lib] Interrupt
make[6]: *** [check-lib] Interrupt
make[5]: *** [check-lib] Interrupt
make[4]: *** [check-lib] Interrupt
make[3]: *** [check-lib] Interrupt
make[2]: *** [check-lib] Interrupt
make[1]: *** [check-lib] Interrupt
make: *** [check-lib] Interrupt
...
-
something strange is going on here
Any ideas?
--
Dylan Beaudette
Soils and Biogeochemistry Graduate Group
University of California at Davis
530.754.7341
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] (Moved from [vox]) Errors in software compilation
Dylan Beaudette wrote:
After copying the GDAL-specific headers to /usr/include:
find . -name *.h -exec cp '{}' /usr/include/ \;
.. make seems to be chugging along fine...
I wouldn't have recommended that. At the very least, a -i option to cp
would seem appropriate, to ensure against clobbering existing files.
Also, a number of those .h files may not have been intended for
installation to system include directories, so you're cluttering things
up in there.
-Micah
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] (Moved from [vox]) Errors in software compilation
Where's your `./configure` step??? -Mark On Wed, 9 Mar 2005, Bill Kendrick wrote: Hi Dylan. This kind of question actually belongs over here on vox-tech, so I've replied here, instead of plain 'vox'... On Wed, Mar 09, 2005 at 03:30:13PM -0800, Dylan Beaudette wrote: Hi everyone, I am using a software package called GDAL here at work, and it compiles fine on my Debian Sarge box... However, the *same* source tree fails to compile on a similar machine running Slackware... snip On your Sarge box, do you have cpl_port.h and/or cpl_error.h anywhere else, besides the 'gdal' build directory? snip g++ -c -o gdalopen.o gdalopen.cpp In file included from gdal_priv.h:190, from gdalopen.cpp:94: gdal.h:177:22: cpl_port.h: No such file or directory gdal.h:178:23: cpl_error.h: No such file or directory snip however: [EMAIL PROTECTED]:~/src/gdal-1.2.5$ locate cpl_port /home/dylan/src/gdal-1.2.5/port/cpl_port.h snip The command invoked above was simply g++ -c -o There were no -I include path directives given. Is this different than on your Sarge box? Also, can you tell (by examining the entire make sequence up to this point) whether Make had dove into the port/ subdirectory? If it was compiling something in the directory above (or some other subdirectory), then it almost certainly wouldn't be able to find the cpl_port.h header. Sorry I can't help more! -- -bill! [EMAIL PROTECTED] I'm anticipating an all-out tactical http://newbreedsoftware.com/ dog-fight, followed by a light dinner. ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech -- Mark K. Kim AIM: markus kimius Homepage: http://www.cbreak.org/ Xanga: http://www.xanga.com/vindaci Friendster: http://www.friendster.com/user.php?uid=13046 PGP key fingerprint: 7324 BACA 53AD E504 A76E 5167 6822 94F0 F298 5DCE PGP key available on the homepage ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] (Moved from [vox]) Errors in software compilation
On Wed, Mar 09, 2005 at 05:58:40PM -0800, Mark K. Kim wrote: Where's your `./configure` step??? In Dylan's original post, he said the configure step worked fine, but that IS a good question. Dylan, can you start fresh and cut-n-paste the initial configure and make steps into an email here? Also, is this app downloadable from anywhere? (I don't remember if you had mentioned an URL in any prev posts) Thx -bill! ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
