The automake/autoconf stuff shouldn't be critical, unless you want to do
some serious Denemo hacking in a Windows environment. The gtk stuff is
important, though; you'll have to pick up the Win32 port of gtk+
(available at http://user.sgic.fi/~tml/gimp/win32/) before you'll be able
to proceed.
Matt
On Fri, 24 Mar 2000, Alain CULOS wrote:
> Hello
>
> I tried to see would I have a go at denemo on windows ...
> I'm afraid there is too many things for me to do to make it work, see the
> configure log below.
>
> Best regards,
> Alain.
>
> ====================
> 13 -> configure
> creating cache ./config.cache
> checking for a BSD compatible install... /USR/BIN/install -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... yes
> checking for working aclocal... missing
> checking for working autoconf... missing
> checking for working automake... missing
> checking for working autoheader... missing
> checking for working makeinfo... found
> checking for gcc... gcc
> checking whether the C compiler (gcc -g -Wall -pedantic ) works... yes
> checking whether the C compiler (gcc -g -Wall -pedantic ) is a cross-compiler...
>
> no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for a BSD compatible install... /USR/BIN/install -c
> checking for bison... bison -y
> checking how to run the C preprocessor... gcc -E
> checking for flex... flex
> checking for flex... (cached) flex
> checking for yywrap in -lfl... no
> checking lex output file root... lex.yy
> checking whether yytext is a pointer... no
> checking for gtk-config... no
> checking for GTK - version >= 1.2.0... no
> *** The gtk-config script installed by GTK could not be found
> *** If GTK was installed in PREFIX, make sure PREFIX/bin is in
> *** your path, or set the GTK_CONFIG environment variable to the
> *** full path to gtk-config.
> configure: error: Cannot find GTK: Is gtk-config in path?
>
>
>
