similar to: devtoolset-4

Hello, my name is Jarek I am new here. I need some clarifications on how to distribute an app developed with devtoolset-4 enabled. I am developing a distributed app in c++ I wanted to upgrade toolchain to use new standard. Is it true that when I compile on centos 6.x with devtoolset enabled then I will be able to run this app on centos 7.x as well? Do I have to install devtoolset on all my

Are you asking if the new libstdc++ is statically linked into your app only for the new functions but your app remains dynamically linked to the old one for the parts of C++ that have remained unchanged, the answer is ?no?. Your app is linked to the new library, period. You can use ldd(1) to prove this to yourself. I am not so sure. That is what I thought, but then I compiled something with a

On May 19, 2016, at 3:30 AM, Jaros?aw Bober <jaroslaw.bober at gmail.com> wrote: > > Do I have to install devtoolset on all my machines that I want to run this > app? Probably, yes. That, or redistribute parts of it with your app, either by cherrypicking files from the devtoolset RPM or statically linking to it. > Or would it use built-in libstdc++ library, linking

On May 20, 2016, at 8:17 AM, Jaros?aw Bober <jaroslaw.bober at gmail.com> wrote: > > ldd gives me: > ldd a.out > linux-vdso.so.1 => (0x00007fff6e5ff000) > libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00000039d8400000) In that case, I don?t see how you can be making use of any C++11/14 features that aren?t implemented by the compiler itself (e.g. type inference via

Is there a way to install devtoolset packages without the bloat of eclipse? I just want the new compiler and toolchain, not a big IDE. BTW devtoolset-3 dependencies are broken in yum with C6 yum install devtoolset-3 ... ---> Package devtoolset-3-perftools.x86_64 0:3.1-12.el6 will be installed --> Processing Dependency: devtoolset-3-dyninst for package:

On Fri, Nov 18, 2016 at 09:47:29AM -0800, Robert Arkiletian wrote > Is there a way to install devtoolset packages without the bloat of eclipse? > > I just want the new compiler and toolchain, not a big IDE. > > BTW devtoolset-3 dependencies are broken in yum with C6 You can do it manually as per the instructions at https://gcc.gnu.org/wiki/InstallingGCC Step 1) Download and

Submitted r204593. On Sun, Mar 23, 2014 at 10:03 PM, Alexey Samsonov <samsonov at google.com>wrote: > Hi Dmitri, > > On Sat, Mar 22, 2014 at 11:50 PM, Dmitri Gribenko <gribozavr at gmail.com>wrote: > >> Hello, >> >> It looks like compiler-rt CMake scripts don't take CMAKE_CXX_FLAGS >> into account. This is because clang_compile and

Hello, It looks like compiler-rt CMake scripts don't take CMAKE_CXX_FLAGS into account. This is because clang_compile and clang_link_shared functions call the newly-built compiler directly, and they don't add those flags. Using CMAKE_CXX_FLAGS is necessary on systems where the C++11-enabled libstdc++ is installed not in the default location. For example, the CentOS buildbot uses:

Has anybody tried (and succeeded) to get gcc 6.3.1 (or devtoolset-6) to work on CentOS 8? In the Animation and Visual Effect industry, gcc 6.3.1 is still the current recommended compiler (see www.vfxplatform.com), and is required to build many plugins. Unfortunately, it is not a "minimum requirement"... It is THE requirement. So I tried to get it from the vault: -- sudo dnf

> > You will need to use the devtoolset builds to do this: > > > There is a gcc 8 .. but not gcc 9 > > https://www.softwarecollections.org/en/scls/rhscl/devtoolset-8/ > > I did install gcc 8 from devtoolset-8 (SCL repo). However I am unable to compile 32-bit programs because devtoolset-8-libstdc++-devel.i686 package is missing from CentOS SCL repository. This is

Hi, I'm currently working on one of my team's project to build LLVM full clang toolchain (Clang, libcxx, libcxxabi) on a CentOS machine. Previously we compiled our codebase with llvm-toolset-7/clang++, which by default takes stdlibc++ to compile and link. And now we'd like to switch to use LLVM clang with libc++. I have built libc++ and libc++abi from source (5.0.1 release) and set

Sorry if I was unclear, I have no problems building clang against a newer gcc for my own purpose. But it doesn't make sense to provide a release binary for clang that's hosted on llvm.org that's ostensibly for "centos6" when it would really be bound to "centos6 plus the SCLO mirror which has the dependency for a newer libstdc++". The glibc 2.14 dependency is a

On 1/3/20 9:37 AM, sthustfo wrote: >> >> You will need to use the devtoolset builds to do this: >> >> >> There is a gcc 8 .. but not gcc 9 >> >> https://www.softwarecollections.org/en/scls/rhscl/devtoolset-8/ >> >> I did install gcc 8 from devtoolset-8 (SCL repo). However I am unable to > compile 32-bit programs because

I want to install several gcc with different versions in centos. The default version of gcc in centos6 is 4.9.3. So I use devtoolset install a higher version of gcc. Then I switch to the higher version of gcc by executing "source /opt/rh/devtoolset-5/enable". But now if I want to switch back to the default gcc, how should I do? By the way, is there any solution to install multiple gcc

On 19/12/16 16:05, Lamar Owen wrote: > On 12/19/2016 08:33 AM, lejeczek wrote: >> devtoolset-4-elfutils-libelf-0.163-2.el7.x86_64 VS >> elfutils-0.166-2.el7.x86_64 >> >> isn't devtool ageing? Could this be the case with more >> packages? >> regards, > devtoolset-6 is available. > somewhere (semi)officially? where? >

It is possible to statically link against libstdc++, yes. I don't quite know all the pieces to the recipe in order to get that to work. It would require changes to the release script in order to get those configuration changes all the way through the third phase build. I don't believe any other tarball release does this, so it would at least be an unconventional release. On Wed, Jun

Hell, Brian, I found a way to install Gcc 5.3 on CentOS 6 without the need to building it from source. You may try it on CentOS 6.0 That's makes clang/llvm won't depends on the newer version of glibc 2.14 The instruction: vim /etc/yum.repos.d/llvm.repo The content: ``` [sclo] name=SCLO baseurl=http://mirror.centos.org/centos/6/sclo/x86_64/rh/ gpgcheck=0 enabled=1 ``` Installation step:

Its seems challenging to maintain applications with a long term vision. For EL6 I want to use devtoolset-3-gcc-c++-4.9.2-6.2.el6.x86_64 to compile some binaries. Here my question: will the binaries execute flawless on a plain EL6 system without additional libraries (stdc++ etc.)? Example: scl enable devtoolset-3 'rpmbuild -ba local-app1.spec' -- Thanks, LF

On 12/19/2016 08:33 AM, lejeczek wrote: > devtoolset-4-elfutils-libelf-0.163-2.el7.x86_64 VS > elfutils-0.166-2.el7.x86_64 > > isn't devtool ageing? Could this be the case with more packages? > regards, devtoolset-6 is available.

hi everyone just a quickie to devel maybe. I'm looking at some bits: devtoolset-4-elfutils-libelf-0.163-2.el7.x86_64 VS elfutils-0.166-2.el7.x86_64 isn't devtool ageing? Could this be the case with more packages? regards, L.