From owner-freebsd-ports@FreeBSD.ORG Wed Apr 1 22:08:16 2015 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BA5DDF1; Wed, 1 Apr 2015 22:08:16 +0000 (UTC) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6E0E513A; Wed, 1 Apr 2015 22:08:16 +0000 (UTC) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3lHM954LBwzZrM; Thu, 2 Apr 2015 00:08:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:mime-version:user-agent:from:from :date:date:message-id:received:received; s=mail; t=1427926087; x=1429740488; bh=038HmK5soZEE/i9c4JsuwxmaJ/mEm7BVnvNFHFCTv/0=; b= RmhQ/gETNUqQsO3+I6+mjC9mRLascocAk/sBxUDz3DmNo8HTjjtNFacOIUcP68Bz 0fcpBT+VrClnKvvU8Z3qkIB9KJAtKY5W0jb42Q+SuJ1Bi8e0wFrh/tS4Udl4pApG aMcuJjs323IVg4bn+VAiCvVSRUiS9z3SZ/9DRqJHG/o= Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id DGVLHINhI1mw; Thu, 2 Apr 2015 00:08:07 +0200 (CEST) Received: from tommy.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Thu, 2 Apr 2015 00:08:07 +0200 (CEST) Message-ID: <551C6C47.1010209@madpilot.net> Date: Thu, 02 Apr 2015 00:08:07 +0200 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Yuri , Jung-uk Kim , "ports@freebsd.org" Subject: Re: Pourdriere produces faulty build results due to bsd.openssl.mk bug References: <551C5C4C.5090707@rawbw.com> <551C6051.4060803@FreeBSD.org> <551C616C.8080503@rawbw.com> <551C636C.1090000@madpilot.net> <551C6509.4010203@rawbw.com> In-Reply-To: <551C6509.4010203@rawbw.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Dirk Meyer , Bryan Drewery X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 22:08:16 -0000 On 04/01/15 23:37, Yuri wrote: > On 04/01/2015 14:30, Guido Falsi wrote: >> Some examples of things that could (and will) go wrong: >> >> - ports silently linking to base ssl due to weirdness in their build >> scripts >> >> - ports linking to other libraries in base which are linked to base ssl, >> causing conflicts >> >> - ports interacting with base parts, which are using base ssl. > > I am going to write the stage-qa test checking for just that: no base > libraries of certain kinds are mixed into the link list. This would be good. What I am most worried about, though, are problems showing up at runtime only on specific configurations or use cases. This would help nailing them down. Check the last entry about asterisk in UPDATING too (I maintain it and that one did hit me on a server of mine) -- Guido Falsi