Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Oct 2015 19:26:54 +0200
From:      Dimitry Andric <dim@FreeBSD.org>
To:        Piotr Kubaj <pkubaj@riseup.net>
Cc:        freebsd-stable@freebsd.org, jakub.lach@mailplus.pl
Subject:   Re: STABLE clang planned update MFC path (3.4.1 STABLE, 3.7.0, CURRENT)
Message-ID:  <9AC8D4B2-2817-4B4C-BB5C-AADB401A01D4@FreeBSD.org>
In-Reply-To: <561A508B.1060408@riseup.net>
References:  <561A508B.1060408@riseup.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_2C580982-8DC5-4B29-BA6E-C7C32A9580E7
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

On 11 Oct 2015, at 14:05, Piotr Kubaj <pkubaj@riseup.net> wrote:
> 
> AFAIK if there had been such plans, they were dropped long ago. The
> reasoning it can't be done (at least for now) is that versions 3.5.0+
> require C++11-capable stack and that would break upgrades from 9-STABLE
> (if the user still uses GCC, as is by default). So, LLVM in stable/10
> will probably be upgraded when stable/9 goes EOL.

If stable/10 had clang 3.5 or higher, you could still upgrade from
stable/9.  It would only require you to do the upgrade in two steps:

* Rebuild and reinstall your stable/9 world using WITH_CLANG,
  WITH_CLANG_IS_CC, and WITH_LIBCPLUSPLUS.  This will install clang
  3.4.1 and libc++, and make clang the default compiler.
* Checkout stable/10 (or even head), and build/install it in the regular
  fashion.

I am personally not against merging newer llvm/clang versions into
stable/10.  But the "silent agreement" has always been that you could
upgrade easily from the latest stable/X to stable/X+1, and the above
two-step process breaks that, or at least makes it more complicated.

Last but not least, note that this would only apply to the architectures
that *can* actually build clang 3.4.1 and libc++ on stable/9.  This is
currently limited to x86, little-endian arm and powerpc (64 bit, I'm
unsure about 32 bit).

-Dimitry


--Apple-Mail=_2C580982-8DC5-4B29-BA6E-C7C32A9580E7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.28

iEYEARECAAYFAlYam+YACgkQsF6jCi4glqOJBwCgj5UMrt8nC7XA8UWfpQvLmIQe
SesAoN2xG7degCYryXx6+1tVSTwz5gOC
=cEFY
-----END PGP SIGNATURE-----

--Apple-Mail=_2C580982-8DC5-4B29-BA6E-C7C32A9580E7--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9AC8D4B2-2817-4B4C-BB5C-AADB401A01D4>