From owner-freebsd-current@freebsd.org Mon Aug 1 21:54:18 2016 Return-Path: Delivered-To: freebsd-current@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 A7048BABB18; Mon, 1 Aug 2016 21:54:18 +0000 (UTC) (envelope-from mandree@freebsd.org) Received: from unimail.uni-dortmund.de (mx1.HRZ.tu-dortmund.de [129.217.128.51]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "unimail.tu-dortmund.de", Issuer "TU Dortmund CA - G01" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DCE01B79; Mon, 1 Aug 2016 21:54:17 +0000 (UTC) (envelope-from mandree@freebsd.org) Received: from [192.168.1.27] ([88.117.234.38]) (authenticated bits=0) by unimail.uni-dortmund.de (8.16.0.16/8.16.0.16) with ESMTPSA id u71LsDJQ002180 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Aug 2016 23:54:14 +0200 (CEST) User-Agent: K-9 Mail for Android In-Reply-To: References: <20160801140804.GD7956@mutt-hardenedbsd> <2061B016-057C-44E9-A982-C0B689861E40@freebsd.org> <20160801143118.GE7956@mutt-hardenedbsd> MIME-Version: 1.0 Subject: Re: security/openvpn build failure on 12-CURRENT/amd64 From: Matthias Andree Date: Mon, 01 Aug 2016 21:54:12 +0000 To: Ngie Cooper , Shawn Webb CC: FreeBSD Current , ports Message-ID: <9D61CE5E-9194-434A-A1AE-79DC21D04DC2@freebsd.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2016 21:54:18 -0000 Hi Ngie, Quite possibly an incompatibility between the port or the upstream software build/self-test rigging with the rather new FreeBSD 12-CURRENT. Since I do not have the latter, I am soliciting patches (through Bugzilla). I am staring at ff. and it does not make sense to me that or why it is failing. I am wondering if it is something specific to 12-CURRENT that does additional patching, or if sed(1) behaves in a different way. Insights welcome. Cheers, Matthias Am 1. August 2016 22:53:47 MESZ, schrieb Ngie Cooper : >On Mon, Aug 1, 2016 at 7:31 AM, Shawn Webb >wrote: > >... > >> HardenedBSD's kernel and world matched and still had the very same >> build error. >> >> Here's the build log: http://pastebin.com/TEBih1Sx > >Confirmed -- why's it looking for tcp6local/udp6local though (this >isn't a valid protocol, and for some odd reason it's being picked up >from the sample config file..?)? Looks like a port bug... >Thanks, >-Ngie > >$ sudo make -C /usr/ports/security/openvpn build >... >PASS: t_lpback.sh >The following test will take about two minutes. >If the addresses are in use, this test will retry up to two times. >Options error: Bad protocol: 'udp6local'. Allowed protocols with >--proto option: [proto-uninitialized] [udp] [tcp-server] [tcp-client] >[tcp] [udp6] [tcp6-server] [tcp6-client] [tcp6] >Use --help for more information. >Options error: Bad protocol: 'udp6local'. Allowed protocols with >--proto option: [proto-uninitialized] [udp] [tcp-server] [tcp-client] >[tcp] [udp6] [tcp6-server] [tcp6-client] [tcp6] >Use --help for more information. >FAIL: t_cltsrv.sh >==================================================== >1 of 2 tests failed >(1 test was not run) >Please report to openvpn-users@lists.sourceforge.net >==================================================== >*** [check-TESTS] Error code 1 >$ grep -r udp6local work/ >work/openvpn-2.3.11/sample/sample-config-files/loopback-client.test:proto >udp6local ::1 >work/openvpn-2.3.11/sample/sample-config-files/loopback-server.test:proto >udp6local ::1