Re: [Mingw-cross-env-list] Build issue with freetds

[Mark Brand]

Hi Volker,

> > There is a build issue with freetds, see the attached log. The
> > critical error is:
> >
> > ------------------------------------------------------------------
> > libtool: link: i686-pc-mingw32-gcc -g -O2 -Wdeclaration-after-statement -o 
> > tdspool.exe config.o main.o member.o user.o util.o @LTLIBPAKCHOIS@  
> > ../server/.libs/libtdssrv.a -L/home/vog/mingw-cross-env/usr/i686-pc-mingw32/lib 
> > /home/vog/mingw-cross-env/usr/i686-pc-mingw32/lib/libiconv.a 
> > /home/vog/mingw-cross-env/usr/i686-pc-mingw32/lib/libgnutls.a -lws2_32 
> > -lpthread /home/vog/mingw-cross-env/usr/i686-pc-mingw32/lib/libgcrypt.a 
> > /home/vog/mingw-cross-env/usr/i686-pc-mingw32/lib/libgpg-error.a -lz
> > i686-pc-mingw32-gcc: error: @LTLIBPAKCHOIS@: No such file or directory
> > ------------------------------------------------------------------
> >
> > It might be sufficient to simply suppress the build of program
> > files such as "tdspool.exe".
>
> Additional note: A very similar issue appears in package vmime.
> See the attached log.

Freetds and vmime buld fine for me on opensuse and squeeze.

My hunch is that the difference on your system has to do with how gnutls 
is configured. I wonder if gnutls configure on your system detects 
libpakchois. On my systems it's not detected, so gnutls uses its 
internal pakchois:

> checking for libpakchois... no
>   *** Pakchois was not found. Will use the included one.
> checking whether to use the included pakchois... yes
> checking for libpakchois... no
>   *** Pakchois was not found. Will use the included one.
> checking whether to use the included pakchois... yes
> checking for libpakchois... no
>   *** Pakchois was not found. Will use the included one.
> checking whether to use the included pakchois... yes


Could you take a look at your gnutls log? Could libpakchois on your host 
system be a factor? Does adding "--with-included-pakchois" solve the 
problem?

Mark