Date: Thu, 02 Apr 2015 00:08:07 +0200 From: Guido Falsi <mad@madpilot.net> To: Yuri <yuri@rawbw.com>, Jung-uk Kim <jkim@freebsd.org>, "ports@freebsd.org" <ports@freebsd.org> Cc: Dirk Meyer <dinoex@freebsd.org>, Bryan Drewery <bdrewery@freebsd.org> Subject: Re: Pourdriere produces faulty build results due to bsd.openssl.mk bug Message-ID: <551C6C47.1010209@madpilot.net> In-Reply-To: <551C6509.4010203@rawbw.com> References: <551C5C4C.5090707@rawbw.com> <551C6051.4060803@FreeBSD.org> <551C616C.8080503@rawbw.com> <551C636C.1090000@madpilot.net> <551C6509.4010203@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?551C6C47.1010209>