From owner-freebsd-current@FreeBSD.ORG Thu Jan 8 18:21:40 2015 Return-Path: Delivered-To: freebsd-current@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 426CB4A4 for ; Thu, 8 Jan 2015 18:21:40 +0000 (UTC) Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) by mx1.freebsd.org (Postfix) with ESMTP id E9DCF5FD for ; Thu, 8 Jan 2015 18:21:39 +0000 (UTC) X-AuditID: 12074422-f79476d000000d9e-bc-54aecaaded63 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id E8.0E.03486.DAACEA45; Thu, 8 Jan 2015 13:21:33 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id t08ILWoL007365; Thu, 8 Jan 2015 13:21:32 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t08ILUTu009182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 8 Jan 2015 13:21:31 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id t08ILUpQ020423; Thu, 8 Jan 2015 13:21:30 -0500 (EST) Date: Thu, 8 Jan 2015 13:21:29 -0500 (EST) From: Benjamin Kaduk To: "Sulev-Madis Silber (ketas)" Subject: Re: HEADS UP: Upgraded clang, llvm and lldb to 3.5.0 In-Reply-To: <54AE72BF.5040405@hot.ee> Message-ID: References: <528C023D-6207-4054-917B-05D4C4E605EC@FreeBSD.org> <12132B80-E31B-4782-B69E-C9B8F6E6F0B8@netapp.com> <54AE72BF.5040405@hot.ee> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjleLIzCtJLcpLzFFi42IRYrdT1117al2IwYnJ3BZz3nxgsnjwZjqr A5PHjE/zWTwezNzGFMAUxWWTkpqTWZZapG+XwJXx8dlXxoLPrBWdzZcZGxjvs3QxcnJICJhI 3F84jw3CFpO4cG89kM3FISSwmEni0penrBDOBkaJE68XsEM4B5kkjpw8BNYiJFAv0Xa7hRnE ZhHQkpjzfjMjiM0moCIx881GsBoRASOJo/c+MYHYzAKGEi/X3WMHsYUFbCUaTt0C6+UUUJN4 vvM4WJxXwFHi2ZyPTBDL3jJK/JjxCywhKqAjsXr/FBaIIkGJkzOfsEAM1ZJYPn0bywRGwVlI UrOQpBYwMq1ilE3JrdLNTczMKU5N1i1OTszLSy3SNdXLzSzRS00p3cQIDlYXpR2MPw8qHWIU 4GBU4uH9cH9tiBBrYllxZe4hRkkOJiVR3v8n1oUI8SXlp1RmJBZnxBeV5qQWH2KU4GBWEuHV 8QTK8aYkVlalFuXDpKQ5WJTEeTf94AsREkhPLEnNTk0tSC2CyWpwcAj0rll9gVGKJS8/L1VJ gvc7yALBotT01Iq0zJwShFImDk6QRTwgi06CLCouSMwtzkyHyJ9i1OVY0L5/JpMQ2CApcV5F kCIBkKKM0jy4ObDk84pRHOhFYd4jIFU8wMQFN+kV0BImoCVZy1eDLClJREhJNTDyNX16/Tzg rt7b/akR7i5K1zWeMQvPcYrn807V65jB7RTtW6q3JcHe4NXKy5JlEuYqC1KlfHjuaLt82f7M R2q11GGb/39OnU9z4Fxz675f2VYzW8WKF1xJs1fq5nEmZoZbex9bbfHa4Xxp1dlVdzP+nfv5 9N/f8vvlTI57AuQLrjV3mBiFuiixFGckGmoxFxUnAgAR32ihGQMAAA== Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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: Thu, 08 Jan 2015 18:21:40 -0000 On Thu, 8 Jan 2015, Sulev-Madis Silber (ketas) wrote: > I don't know... if 9.x can't be used to build 11.x / CURRENT anymore, > maybe this should be put to UPDATING (that 9.x is not supported) and I > just upgrade to 10.x... which would solve everything (hopefully). I have no specific data about this specific case, but the advertised procedure for upgrading between major branches is to update to the tip of the starting branch before attempting the major version jump, i.e., update to the tip of stable/9 before attempting to go to stable/10 or head. Given that 9.3 is the latest release from the 9.x series, it's not immediately clear (without doing some research) whether that will actually help in this specific case. -Ben Kaduk