Date: Sat, 18 Jun 2016 20:09:42 +0200 From: Guido Falsi <mad@madpilot.net> To: freebsd-ports@freebsd.org Subject: Re: Why central builds are performed on 10.1 with broken/different compared to 10,3 compiler? Message-ID: <15db9574-831c-7055-895f-7dcbd2f9a144@madpilot.net> In-Reply-To: <ae480e24-4510-f203-4071-e05e481e6d48@rawbw.com> References: <64e51a34-fced-4f7f-2a3f-9508c6c24b39@rawbw.com> <20160618172005.GA19494@home.opsec.eu> <ae480e24-4510-f203-4071-e05e481e6d48@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/18/16 19:35, Yuri wrote: > On 06/18/2016 10:20, Kurt Jaeger wrote: >>> >There are two questions: >>> >1. Why clang36 works differently on 10.1 and 10.3? >> Good question. Additional patches went into 10.3, probably ? > > > It looks like compiler on 10.1 is broken, because c++11 or c++14 isn't > (fully) supported there. > Now these fallout messages will keep coming and nothing can be done to > fix them. FreeBSD 10.1 is anyway a supported version, it's not superseded by 10.3, so, if your port breaks there, you should try to fix it, or mark it broken explicitly. The cluster always uses the oldest supported dot release of every branch to build packages, because in this way packages can be used on all newer dot releases. The opposite could not be true. Finally, please note that starting with the upcoming 11.0 release the support policy is going to change and this kind of situation cannot happen with the new policy. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15db9574-831c-7055-895f-7dcbd2f9a144>