Re: Crossbuilding AbiWord for Win32

Ryan Pavlik wrote:
> Robert Staudinger wrote:
>
>> On Jan 9, 2008 2:32 AM, Ryan Pavlik <abiryan@ryand.net> wrote:
>>
>> [...]
>>
>>
>>
>>> Here's the thing that confuses me - I have automake 2.59 and autoconf
>>> 1.8.2 already installed and in the MSYS path - it shouldn't have trouble
>>> finding them.
>>>
>>> Any clues?
>>>
>>>
>> Sorry, my win32 fu is close to non-existant. However, it indeed looks
>> like an environment setup issue.
>> Presumably running the commands executed by autogen.sh manually in the
>> shell works?
>>
>> - Rob
>>
>>
>>
> Well, it's because the msys automake wants perl in /bin/perl, whereas I
> was using activestate installed outside. Installing the DTK first then
> the new automake/autoconf, I get quite a bit farther:
> Administrator@GAMMA2KVM /c/src/abitrunk/abi
> $ CPPFLAGS="-I/c/src/abitrunk/libs/boost/ -I/c/src/abitrunk/libs/asio/"
> ./autog
> en.sh
> + Entering source dir . ...
> + Running libtoolize --force --copy
> You should add the contents of `/usr/share/aclocal/libtool.m4' to
> `aclocal.m4'.
> MINGW32_NT-5.0
> + Win32 detected, skipping autoheader
> automake (GNU automake) 1.8.2
> + Running autoheader ...
> + Creating aclocal.m4: aclocal -I ./plugins/collab -I ./plugins/collab
> + Running automake ...
> + Creating configure...
>
> * warning: possible errors while running automake - check autogen.err
>
> + Leaving source dir . ...
> Running ./configure --enable-maintainer-mode ...
> checking build system type... i686-pc-mingw32
> checking host system type... i686-pc-mingw32
> checking target system type... i686-pc-mingw32
> checking for a BSD-compatible install... /bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for gcc... gcc
> checking for C compiler default output file name... a.exe
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables... .exe
> 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
> ./configure: AC_PROG_OBJC: command not found
> checking for a BSD-compatible install... /bin/install -c
> checking for egrep... grep -E
> checking for ld used by GCC... c:/mingw/mingw32/bin/ld.exe
> checking if the linker (c:/mingw/mingw32/bin/ld.exe) is GNU ld... yes
> checking for c:/mingw/mingw32/bin/ld.exe option to reload object files... -r
> checking for BSD-compatible nm... /mingw/bin/nm
> checking for a sed that does not truncate output... /bin/sed
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... file_magic ^x86 archive
> import| ^x86 DLL
> checking for dlltool... dlltool
> checking for as... as
> checking for objdump... objdump
> 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... no
> checking dlfcn.h presence... no
> checking for dlfcn.h... no
> 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... 8192
> checking command to parse /mingw/bin/nm output from gcc object... ok
> checking for objdir... .libs
> checking for ranlib... ranlib
> checking for strip... strip
> checking if gcc static flag works... yes
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -DDLL_EXPORT
> checking if gcc PIC flag -DDLL_EXPORT works... yes
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (c:/mingw/mingw32/bin/ld.exe) supports
> shared li braries... yes
> checking whether -lc should be explicitly linked in... yes
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking dynamic linker characteristics... Win32 ld.exe
> 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 whether the g++ linker (c:/mingw/mingw32/bin/ld.exe) supports
> shared li braries... yes
> checking for g++ option to produce PIC... -DDLL_EXPORT
> checking if g++ PIC flag -DDLL_EXPORT works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (c:/mingw/mingw32/bin/ld.exe) supports
> shared li braries... yes
> checking whether -lc should be explicitly linked in... yes
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking dynamic linker characteristics... Win32 ld.exe
> 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 option to produce PIC... -DDLL_EXPORT
> checking if PIC flag -DDLL_EXPORT works... no
> checking if supports -c -o file.o... no
> checking whether the linker (c:/mingw/mingw32/bin/ld.exe) supports
> shared libra ries... yes
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking dynamic linker characteristics... ./configure:
> -print-search-dirs: comm and not found
> ./configure: -print-search-dirs: command not found
> Win32 ld.exe
> checking whether ln -s works... yes
> checking for platform and toolkit... win / win
> ./configure: line 18086: syntax error near unexpected token
> `$libgnomeprintui_re q'
> ./configure: line 18086: ` PKG_CHECK_EXISTS(
> $libgnomeprintui_req , '
>
>
>
> The autogen.err file referred to:
> Administrator@GAMMA2KVM /c/src/abitrunk/abi
> $ cat autogen.err
> /usr/share/aclocal/autoopts.m4:22: warning: underquoted definition of
> AG_PATH_AUTOOPTS
> run info '(automake)Extending aclocal'
> or see
> http://sources.redhat.com/automake/automake.html#Extending%20aclocal
> configure.in: installing `./install-sh'
> configure.in: installing `./missing'
> Makefile.am: installing `./INSTALL'
> goffice-bits/Makefile.am: installing `./compile'
> goffice-bits/Makefile.am: installing `./depcomp'
> configure.in:63: error: possibly undefined macro: AC_PROG_OBJC
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
> configure.in:215: error: possibly undefined macro: AC_MSG_ERROR
>
>
> Information on how to proceed would be greatly appreciated - thanks for
> your help!
>
> Ryan
>
>
Replying to myself for the record - I needed to set the ACLOCAL_FLAGS to
include an ACLOCAL path (to get pkg.m4) The complete command line is now:

|PKG_CONFIG_PATH=/mingw/lib/pkgconfig CPPFLAGS="-I../libs/boost/
-I../libs/asio/" ACLOCAL_FLAGS="-I /mingw/share/aclocal/" ./autogen.sh|

(Instructions in progress at
http://cleardefinition.com/page/Building_AbiWord_2_8_on_Windows/ to be
moved to SVN when they are more or less complete)

I see we are now using Enchant everywhere (it shows up as a dependency)
- is this a conscious choice? It will require that Aspell and an aspell
dict be installed on Windows, unless we can get it to use the
ispell/"abispell" stuff we're packaging for 2.6 and prior.

Exciting stuff!

-- 
Ryan Pavlik
www.cleardefinition.com