From owner-freebsd-ports@freebsd.org Thu Nov 9 19:03:35 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F1A8E58DF1 for ; Thu, 9 Nov 2017 19:03:35 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 02F8273A80 for ; Thu, 9 Nov 2017 19:03:35 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: by mailman.ysv.freebsd.org (Postfix) id F3743E58DF0; Thu, 9 Nov 2017 19:03:34 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2FB0E58DED for ; Thu, 9 Nov 2017 19:03:34 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from mx2.mailbox.org (mx2.mailbox.org [80.241.60.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.mailbox.org", Issuer "SwissSign Server Silver CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B055973A7F for ; Thu, 9 Nov 2017 19:03:33 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.mailbox.org (Postfix) with ESMTPS id 5887C4C988; Thu, 9 Nov 2017 20:03:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mailbox.org; h= content-type:content-type:mime-version:references:in-reply-to :subject:subject:from:from:message-id:date:date:received; s= mail20150812; t=1510254201; bh=2gulu5jw6zs0TEF+r3MYRAPJl376NWTSA NplqKpx2hs=; b=Tskq+6ux0iEhtMoVAlfZmBbTLNbqIQ/w4b6/BTTQvq8MbyEYj 0UcLTGfzXE3NtfB5UW6E8rH4Nx8ckzHYCrwK3WuSMlIx1r9wNxpGge4u5SgXvkpw a9DxFGOsXE5+r0L8UbR+9AB+jB3NpJWDsHdVAJoS+4uBYJyEoEjJbIbbSz8RnNAP 8tzIgZIeKzUcdDKcAQQO09WXhpAhkJVJoiRjKzI0RuIW1E3Tt5crxlrye2611/kO JLTsZBzcco5Ll9RxrED8vtgD3Uwhnl2lKUeOIMjBXxl+9eqjjXN8OTjHI/HQEGVN 9348xPeXhcl0ZM7TGNe0HDhqBdZUyYOOE2LCw== X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by gerste.heinlein-support.de (gerste.heinlein-support.de [91.198.250.173]) (amavisd-new, port 10030) with ESMTP id 8cBWwck7x2j2; Thu, 9 Nov 2017 20:03:21 +0100 (CET) Date: Thu, 09 Nov 2017 20:03:19 +0100 Message-ID: <87shdns2a0.wl-herbert@mailbox.org> From: "Herbert J. Skuhra" To: Kurt Jaeger Cc: freebsd-ports@dan.me.uk, ports@FreeBSD.org Subject: Re: mail/opendkim In-Reply-To: <20171109174217.GB49221@home.opsec.eu> References: <87tvy3sctp.wl-herbert@mailbox.org> <20171109174217.GB49221@home.opsec.eu> MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Nov 2017 19:03:35 -0000 On Thu, 09 Nov 2017 18:42:17 +0100, Kurt Jaeger wrote: > > Hi! > > > Bugzilla[1] lists three new and one open PR for mail/opendkim. Is the > > port still maintained? > > Yes, but some of the PRs are difficult to parse. > > > The port does not build with security/openssl-devel. There is a patch: > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828466 > > https://sourceforge.net/p/opendkim/patches/37/ > > https://git.archlinux.org/svntogit/community.git/plain/trunk/openssl_1.1.0_compat.patch?h=packages/opendkim > > > > The patch requires autoreconf. > > I generated a patch using that patch in > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223568 Thanks. I've just found out that the patch breaks the build with libressl. :-( Maybe the following lines are required: .if ${SSL_DEFAULT:Mopenssl-devel} USES+= autoreconf EXTRA_PATCHES= ${FILESDIR}\extra-patch-configure.ac \ ${FILESDIR}\extra-patch-opendkim_opendkim-crypto.c .endif > > Can you/anyone commit it? > > A simple build-test looks OK (but fails if LUA is enabled), > but I can't run-test it. Can you do it ? > > With LUA I've seen some strange thing on a simple build-test > on a loaded box, must re-do it in poudriere. Hmm, autoreconf obviously overwrites the LUA changes to configure. :-( pre-configure: ${REINPLACE_CMD} -e '/LIBLUA_LIBS/s/lua5\.[0-9]/lua-${LUA_VER}/' \ -e '/PKG_CONFIG/s/lua5\.[0-9]/lua-${LUA_VER}/' \ -- Herbert