From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: [PATCH] Fix configure script to properly detect gmime-2.6 if
	available.
Date: Thu,  8 Mar 2012 08:45:01 -0800
Message-Id: <1331225101-24385-1-git-send-email-jrollins@finestructure.net>
Precedence: list

Previously, the configure script would appear to detect gmime-2.6 if
present.  However, the binaries would end up being compiled against
gmime-2.4.  The addition of a break fixes things so that now gmime-2.6
will be used if available, falling back to gmime-2.4.
---
I was wondering why I wasn't seeing any of the problems bremner is
reporting, even though I thought I had been using gmime-2.6 for the
last month.  Apparently I had actually been using gmime-2.4 because of
this bug in the configure script.  Linking will now be correct after
reconfigure.

 configure |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/configure b/configure
index 8b85b9d..dedb7d8 100755
--- a/configure
+++ b/configure
@@ -281,6 +281,7 @@ for gmimepc in gmime-2.6 gmime-2.4; do
 	have_gmime=1
 	gmime_cflags=$(pkg-config --cflags $gmimepc)
 	gmime_ldflags=$(pkg-config --libs $gmimepc)
+	break
     fi
 done
 if [ "$have_gmime" = "0" ]; then
-- 
1.7.9.1