Xapian discuss - Dec 2016 - swig-3.0.7 for xapian-bindings to tcl

I recently wrote a post on installing "Git for Windows" on a legacy XP
SP3 Home box.

http://nurmi-labs.blogspot.com/2016/11/git.html

I added some missing files from the MSYS2 packages which were removed for the
downloadable
"Git for Windows" installer and a compiler and some additional
libraries.

For other utilities (bison, flex, info, m4, make, and csh/tcsh), and code I
would compile,
I setup an extra directory tree as C:\MSYS2 and used an /etc/fstab mount point
for that
directory mounted on /usr/local; wanting to distinguish between the basic
"Git for Windows"
plus compiler and libraries directory tree which was in C:\Programmer\Git; these
utilities
and shells being available from the appropriate i686 or the x86_64 webpages.

https://sourceforge.net/projects/msys2/files/REPOS/MSYS2/i686/
https://sourceforge.net/projects/msys2/files/REPOS/MSYS2/x86_64/

"Git for Windows" shipped with a Perl compiled for the msys
environment, not the mingw-w64-i686 environment which the Tcl/TK it shipped was
compiled for; Python and Python3 compiled for the
mingw-w64-i686 environment are separately available as packages from the
appropriate i686 or the
x86_64 webpages.

https://sourceforge.net/projects/msys2/files/REPOS/MINGW/i686/
https://sourceforge.net/projects/msys2/files/REPOS/MINGW/x86_64/

In the last section of my post swig is mentioned, and my questions are 1)
whether crypt is
significant to allocate for, the "Git for Windows" shipped libcrypt
1.3-1 being compiled
for the msys environment - obviously one would need to add the dev package - for
swig to
be compiled for use by xapian-bindings, and 2) the subject about gethostbyname
and socket
found in the below output seems to warrant some clarification pertaining to the
MSYS2 and/or
MinGW environments, and a swig compiled for use by xapian-bindings?

The dlopen issue I believe is POSIX and therefore not relevant to a
mingw-w64-i686
(or mingw-w64-x86_64) environment; and furthermore -lieee returns 'yes'
on GNU/Linux.

I should say that I am unconcerned whether potential responses pertain to 1.4.1
stable
or to 1.2.x old stable series.

Eric at Erics-Netbook MINGW32 ~
$ cd /c/WORK/swig-3.0.7

Eric at Erics-Netbook MINGW32 /c/WORK/swig-3.0.7
$ export
PATH=/mingw32/bin:/usr/local/bin:/usr/bin:/bin:\
> /c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:\
> /usr/bin/vendor_perl:/usr/bin/core_perl
Eric MINGW32 /c/WORK
$ ./configure --prefix=/c/MSYS2 --with-tclconfig=/mingw32/lib --without-perl5

...

checking for dlopen in -ldl... no
checking for shl_load in -ldld... no
checking for library containing t_open... no
checking for library containing gethostbyname... no
checking for library containing socket... no
checking for swill_init in -lswill... no
checking for main in -lieee... no
checking for crypt in -lcrypt... no
checking for pkg-config... pkg-config
checking for Tcl configuration... found /mingw32/lib/tclConfig.sh
checking for Tcl header files... -isystem /mingw32/include/tcl8.6
checking for Tcl library... -L/mingw32/lib -ltcl86
checking for python... no

...

The SWIG test-suite and examples are configured for the following languages:
tcl


Eric at Erics-Netbook MINGW32 /c/WORK/swig-3.0.7
$

On Sun, Dec 04, 2016 at 12:16:03PM +0000, Eric Lindblad
wrote:
> In the last section of my post swig is mentioned, and my questions are 1)
whether crypt is
> significant to allocate for, the "Git for Windows" shipped
libcrypt 1.3-1 being compiled
> for the msys environment - obviously one would need to add the dev package
- for swig to
> be compiled for use by xapian-bindings
Not sure what you're asking here - searching for "crypt" in your
blog post only
finds one mention.  But I don't believe swig needs any crypto functionality.
> and 2) the subject about gethostbyname and socket
> found in the below output seems to warrant some clarification pertaining to
the MSYS2 and/or
> MinGW environments, and a swig compiled for use by xapian-bindings?
> 
> The dlopen issue I believe is POSIX and therefore not relevant to a
mingw-w64-i686
> (or mingw-w64-x86_64) environment; and furthermore -lieee returns
'yes' on GNU/Linux.
I wouldn't worry about things a configure script does or doesn't find in
its
checks.  The whole point of these checks is that not all platforms have the
features being probed for - if they were reliably present, there would be
no point in probing for them.  Only worry about them if you get an error
building the software.
> Eric at Erics-Netbook MINGW32 ~
> $ cd /c/WORK/swig-3.0.7
You shouldn't be downloading and building some arbitrary version of SWIG
to use to build Xapian's bindings.

If you build from a xapian-bindings tarball, then you already have the
files SWIG would generate.

If you are building from git, use the "bootstrap" script at the top
level,
then run the top level configure script which it generates and run
"make"
at the top level.  The "bootstrap" script will perform a git clone of
the
SWIG git repo and select a point in the history which is "known good"
for
building all of Xapian's bindings.

Cheers,
    Olly