[mapguide-users] Problems with new fdo ogr build on Ubuntu 6.06
Jack Lee
jack.lee at autodesk.com
Fri Oct 26 08:37:37 EDT 2007
Hi,
Yes. You probably don't have that file on your machine.
-----Original Message-----
From: mapguide-users-bounces at lists.osgeo.org [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Jo Cook
Sent: Friday, October 26, 2007 8:34 AM
To: mapguide-users at lists.osgeo.org
Subject: RE: [mapguide-users] Problems with new fdo ogr build on Ubuntu 6.06
Hi Jack,
Sorry for being a n00b about this, but do you mean using subversion, eg just
checking I have the most up to date version of that file or something else?
Thanks
Jo
Jack Lee-3 wrote:
>
> Hi,
>
> We had a problem with building the PostGIS provider. I think this error is
> referring to the PostGIS provider.
> You should do a sync on Providers/PostGIS/Doc/Makefile.am.
>
>
> -----Original Message-----
> From: mapguide-users-bounces at lists.osgeo.org
> [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Jo Cook
> Sent: Friday, October 26, 2007 4:50 AM
> To: mapguide-users at lists.osgeo.org
> Subject: [mapguide-users] Problems with new fdo ogr build on Ubuntu 6.06
>
>
> Hi All,
>
> Having just discovered that the postgis and ogr fdo connectors have been
> added to the fdo svn trunk (and therefore been made available to the
> standard mapguide build) I thought I would give it a go building on Ubuntu
> 6.06 as per the instructions on the wiki.
>
> Build_Thirdparty went through without a hitch, all I needed to do was add
> a
> /usr/local/fdo-3.3.0 directory and give it the appropriate ownership.
> However, build_linux failed at (I think) the ogr point and I can't really
> figure out what the problem is from the build log. The section relating to
> the ogr build is as follows:
>
> =======================
>
> make[1]: Entering directory `/home/joc/fdosvn/Providers/OGR'
> test -z "/usr/local/fdo-3.3.0/lib" || mkdir -p --
> "/usr/local/fdo-3.3.0/lib"
> /bin/sh ./libtool --mode=install /usr/bin/install -c 'libOGRProvider.la'
> '/usr/local/fdo-3.3.0/lib/libOGRProvider.la'
> libtool: install: warning: relinking `libOGRProvider.la'
> (cd /home/joc/fdosvn/Providers/OGR; /bin/sh ./libtool --tag=CXX
> --mode=relink g++ -MMD -MT -D__USE_GNU -DLINUX -DLINUX_IA32 -o
> libOGRProvider.la -rpath /usr/local/fdo-3.3.0/lib -shared -release 3.3.0
> -L/home/joc/fdosvn/Thirdparty/gdal/lib -L../../Thirdparty/gdal/lib
> OgrFdoUtil.lo OgrProvider.lo ProjConverter.lo
> ../../Fdo/Unmanaged/Src/libFDO.la -lgdal )
> g++ -shared -nostdlib
> /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../lib/crti.o
> /usr/lib/gcc/i486-linux-gnu/4.0.3/crtbeginS.o .libs/OgrFdoUtil.o
> .libs/OgrProvider.o .libs/ProjConverter.o -Wl,--rpath
> -Wl,/usr/local/fdo-3.3.0/lib -L/home/joc/fdosvn/Thirdparty/gdal/lib
> -L/usr/local/fdo-3.3.0/lib -lFDO -lgdal
> -L/usr/lib/gcc/i486-linux-gnu/4.0.3
> -L/usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../lib
> -L/usr/lib/gcc/i486-linux-gnu/4.0.3/../../.. -L/lib/../lib
> -L/usr/lib/../lib
> -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i486-linux-gnu/4.0.3/crtendS.o
> /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../lib/crtn.o -Wl,-soname
> -Wl,libOGRProvider-3.3.0.so -o .libs/libOGRProvider-3.3.0.so
> /usr/bin/install -c .libs/libOGRProvider-3.3.0.soT
> /usr/local/fdo-3.3.0/lib/libOGRProvider-3.3.0.so
> (cd /usr/local/fdo-3.3.0/lib && { ln -s -f libOGRProvider-3.3.0.so
> libOGRProvider.so || { rm -f libOGRProvider.so && ln -s
> libOGRProvider-3.3.0.so libOGRProvider.so; }; })
> /usr/bin/install -c .libs/libOGRProvider.lai
> /usr/local/fdo-3.3.0/lib/libOGRProvider.la
> PATH="$PATH:/sbin" ldconfig -n /usr/local/fdo-3.3.0/lib
> ----------------------------------------------------------------------
> Libraries have been installed in:
> /usr/local/fdo-3.3.0/lib
>
> If you ever happen to want to link against installed libraries
> in a given directory, LIBDIR, you must either use libtool, and
> specify the full pathname of the library, or use the `-LLIBDIR'
> flag during linking and do at least one of the following:
> - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
> during execution
> - add LIBDIR to the `LD_RUN_PATH' environment variable
> during linking
> - use the `-Wl,--rpath -Wl,LIBDIR' linker flag
>
> See any operating system documentation about shared libraries for
> more information, such as the ld(1) and ld.so(8) manual pages.
> ----------------------------------------------------------------------
> make[1]: Nothing to be done for `install-data-am'.
> make[1]: Leaving directory `/home/joc/fdosvn/Providers/OGR'
> acinclude.m4:7: warning: underquoted definition of FDO_HELP_STRING
> run info '(automake)Extending aclocal'
> or see
> http://sources.redhat.com/automake/automake.html#Extending-aclocal
> acinclude.m4:12: warning: underquoted definition of FDO_SUBST
> acinclude.m4:19: warning: underquoted definition of FDO_FAST_OUTPUT
> acinclude.m4:25: warning: underquoted definition of FDO_GEN_CONFIG_VARS
> acinclude.m4:66: warning: underquoted definition of FDO_GENERATE_MAKEFILES
> acinclude.m4:73: warning: underquoted definition of FDO_OUTPUT
> acinclude.m4:82: warning: underquoted definition of FDO_DEFINE_TYPE_RLIM_T
> acinclude.m4:107: warning: underquoted definition of
> FDO_SUBST_EXPANDED_ARG
> acinclude.m4:114: warning: underquoted definition of FDO_EXPORT_ARGUMENTS
> Putting files in AC_CONFIG_AUX_DIR, `../..'.
> configure.in:66: required file `Doc/Makefile.in' not found
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> 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 style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking for bison... bison -y
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for egrep... grep -E
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for /usr/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... no
> checking for f77... no
> checking for xlf... no
> checking for frt... no
> checking for pgf77... no
> checking for fort77... no
> checking for fl32... no
> checking for af77... no
> checking for f90... no
> checking for xlf90... no
> checking for pgf90... no
> checking for epcf90... no
> checking for f95... no
> checking for fort... no
> checking for xlf95... no
> checking for ifc... no
> checking for efc... no
> checking for pgf95... no
> checking for lf95... no
> checking for gfortran... no
> checking whether we are using the GNU Fortran 77 compiler... no
> checking whether accepts -g... no
> 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 supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC
> checking if gcc PIC flag -fPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (/usr/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... no
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking whether the g++ linker (/usr/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++ static flag -static works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/bin/ld) supports shared libraries...
> yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> appending configuration tag "F77" to libtool
> configure: Using optimized configuration
> configure: creating ./config.status
> config.status: error: cannot find input file: Makefile.in
> make: *** No targets specified and no makefile found. Stop.
> make: *** No rule to make target `install'. Stop.
> joc at ubuntu:~/fdosvn$ exit
>
> ===========================
>
> So I can see that there is a problem quite early on where it says:
>
> "configure.in:66: required file `Doc/Makefile.in' not found"
>
> But I don't really know what to do about that- so if anyone can give me
> some
> pointers I'd appreciate it greatly.
>
> Many thanks
>
> Jo
>
> PS I will post this on the fdo list if I don't get any replies here but
> don't want to double-post if I can avoid it...
> --
> View this message in context:
> http://www.nabble.com/Problems-with-new-fdo-ogr-build-on-Ubuntu-6.06-tf4695940s16610.html#a13423077
> Sent from the MapGuide Users mailing list archive at Nabble.com.
>
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
>
>
--
View this message in context: http://www.nabble.com/Problems-with-new-fdo-ogr-build-on-Ubuntu-6.06-tf4695940s16610.html#a13426256
Sent from the MapGuide Users mailing list archive at Nabble.com.
_______________________________________________
mapguide-users mailing list
mapguide-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
More information about the mapguide-users
mailing list