On Mon, Oct 03, 2016 at 09:04:15AM +0200, Joerg Sonnenberger via llvm-dev wrote:> On Sun, Oct 02, 2016 at 11:09:08PM +0000, Zachary Turner via llvm-dev wrote: > > The BSDs don't seem as much of an issue. FreeBSD 10 and 11 both have LLVM > > 3.9 and GCC 4.9. NetBSD 6.1.5 and 7.0 both have GCC 5.3 and LLVM 3.8. > > Open BSD has a very old GCC, but distrowatch claims that it also has LLVM > > 3.8. > > NetBSD 6.1.5 has GCC 4.5 in base, 7.0 has 4.8. Clang is not included the > default for either.Another feedback from a downstream user: in order to build our llvm-based compiler once and have it run on a large variety of Linux machines, we're using ubuntu trusty as build environment, which has the nice property of using a rather old GLIBC version. Ubuntu trusty ships by default with g++-4.8. This can obviously be worked around though.
On Mon, 3 Oct 2016 09:30:08 +0200 serge guelton via llvm-dev <llvm-dev at lists.llvm.org> wrote:> On Mon, Oct 03, 2016 at 09:04:15AM +0200, Joerg Sonnenberger via llvm-dev wrote: > > On Sun, Oct 02, 2016 at 11:09:08PM +0000, Zachary Turner via llvm-dev wrote: > > > The BSDs don't seem as much of an issue. FreeBSD 10 and 11 both have LLVM > > > 3.9 and GCC 4.9. NetBSD 6.1.5 and 7.0 both have GCC 5.3 and LLVM 3.8. > > > Open BSD has a very old GCC, but distrowatch claims that it also has LLVM > > > 3.8. > > > > NetBSD 6.1.5 has GCC 4.5 in base, 7.0 has 4.8. Clang is not included the > > default for either. > > Another feedback from a downstream user: in order to build our > llvm-based compiler once and have it run on a large variety of Linux > machines, we're using ubuntu trusty as build environment, which has > the nice property of using a rather old GLIBC version. Ubuntu trusty > ships by default with g++-4.8.We use CentOS 5 for the same reason. The compiler is gcc 4.8.2, coming from the Developer Toolset 2. Bumping C++ requirements to C++14 may force us to switch our build machine to CentOS 6, and abandon support for users of older versions of RHEL and CentOS. Regards Antoine.
On 10/03/2016 03:40 AM, Antoine Pitrou via llvm-dev wrote:> On Mon, 3 Oct 2016 09:30:08 +0200 > serge guelton via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> On Mon, Oct 03, 2016 at 09:04:15AM +0200, Joerg Sonnenberger via llvm-dev wrote: >>> On Sun, Oct 02, 2016 at 11:09:08PM +0000, Zachary Turner via llvm-dev wrote: >>>> The BSDs don't seem as much of an issue. FreeBSD 10 and 11 both have LLVM >>>> 3.9 and GCC 4.9. NetBSD 6.1.5 and 7.0 both have GCC 5.3 and LLVM 3.8. >>>> Open BSD has a very old GCC, but distrowatch claims that it also has LLVM >>>> 3.8. >>> NetBSD 6.1.5 has GCC 4.5 in base, 7.0 has 4.8. Clang is not included the >>> default for either. >> Another feedback from a downstream user: in order to build our >> llvm-based compiler once and have it run on a large variety of Linux >> machines, we're using ubuntu trusty as build environment, which has >> the nice property of using a rather old GLIBC version. Ubuntu trusty >> ships by default with g++-4.8. > We use CentOS 5 for the same reason. The compiler is gcc 4.8.2, coming > from the Developer Toolset 2. > > Bumping C++ requirements to C++14 may force us to switch our build > machine to CentOS 6, and abandon support for users of older versions of > RHEL and CentOS.We have a similar setup and would have similar problems, but at a slightly later gcc version. We're currently using gcc-4.9.2. We could probably work around this, but I'd really rather not do so unless there's a good reason. (I know the current discussion is around moving to 4.9 as a baseline. We'd be fine with this, I'm mostly chiming in since 5.2 was mentioned earlier in the thread and that would be a problem.) Philip