Date: Wed, 01 Apr 2015 15:27:57 -0700 From: Yuri <yuri@rawbw.com> To: Guido Falsi <mad@madpilot.net>, 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: <551C70ED.1040809@rawbw.com> In-Reply-To: <551C6C47.1010209@madpilot.net> References: <551C5C4C.5090707@rawbw.com> <551C6051.4060803@FreeBSD.org> <551C616C.8080503@rawbw.com> <551C636C.1090000@madpilot.net> <551C6509.4010203@rawbw.com> <551C6C47.1010209@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/01/2015 15:08, Guido Falsi wrote: > 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. Such stage-qa check will currently likely fail on many ports. It can help in testing after the removal of the said dependencies on base OpenSSL, and should be permanently enabled afterwards. Currently VirtualBox is broken when installed out of the default package repository. I also observed that rebuilding only curl locally doesn't help for other broken things, and one also needs to rebuild kde4-network, and maybe other things. So the problem is quite nasty. It has been triggered by some curl update during March. > > Check the last entry about asterisk in UPDATING too (I maintain it and > that one did hit me on a server of mine) Yes, things shouldn't need to be disabled just because of this conflict. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?551C70ED.1040809>