>From e632bf2c2cbe38ed0b606dc166255dc22c51fc45 Mon Sep 17 00:00:00 2001
From: Vadim Zeitlin <address@hidden>
Date: Thu, 31 Dec 2015 02:43:36 +0100
Subject: [PATCH 1/2] Don't look for Boost libraries with "-mgw" prefix only in
 configure

The libraries don't have this suffix when they're cross-compiled, so don't
enforce its use when using *-*-mingw32 host. The suffix can always be
specified manually for the platforms that need it.
---
 configure.ac | 13 -------------
 1 file changed, 13 deletions(-)

diff --git a/configure.ac b/configure.ac
index 3856e6f..a381d87 100644
--- a/configure.ac
+++ b/configure.ac
@@ -44,12 +44,10 @@ case "${host}" in
         ;;
 
     *-*-cygwin* )
-        USE_CYGWIN=1
         USE_WINDOWS=1
         ;;
 
     *-*-mingw32* )
-        USE_MINGW32=1
         USE_WINDOWS=1
         ;;
 esac
@@ -346,17 +344,6 @@ AC_CHECK_HEADER([boost/type_traits.hpp],
     [AC_MSG_ERROR([Boost headers not found, $errmsg])]
 )
 
-dnl By default no particular toolkit suffix should be needed when linking
-dnl against boost libraries. Except for mingw where it seems to be
-dnl required. Because under mingw default installation does _not_ create
-dnl a symbolic link without the tollkit suffix (-mgw), at least
-dnl for the version 1.33.1. Therefore explicitly set it if no toolkit specified.
-if test "x$lmi_boost_toolkit" = "x"; then
-    if test "x$USE_MINGW32" = "x1"; then
-        lmi_boost_toolkit=mgw
-    fi
-fi
-
 dnl The default boost library name should be used unless otherwise specified
 dnl via --with-boost-tookit options, in which case we need to add
 dnl toolkit suffix to the library name (example -lboost_filesystem-gcc-mt).
-- 
2.5.1