From e13439bd57b4c95948edc5aa517dcb5c4422fc67 Mon Sep 17 00:00:00 2001
From: Michael Gehring <mg@ebfe.org>
Date: Mon, 22 Feb 2016 13:01:11 +0100
Subject: [PATCH] libmill: don't set _FORTIFY_SOURCE

libmill does quite a bit of stack trickery that triggers assertions when
build with our default _FORTIFY_SOURCE=2
---
 srcpkgs/libmill/template | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/libmill/template b/srcpkgs/libmill/template
index 8163304400d..bb330f8e7f7 100644
--- a/srcpkgs/libmill/template
+++ b/srcpkgs/libmill/template
@@ -1,7 +1,7 @@
 # Template file for 'libmill'
 pkgname=libmill
 version=1.6
-revision=1
+revision=2
 build_style=gnu-configure
 hostmakedepends="automake libtool"
 short_desc="Go-style concurrency in C"
@@ -15,6 +15,11 @@ pre_configure() {
 	autoreconf -fi
 }
 
+do_configure() {
+	export CFLAGS="${CFLAGS/-D_FORTIFY_SOURCE=?/}"
+	${configure_script} ${configure_args}
+}
+
 post_install() {
 	vlicense COPYING
 }