similar to: devtoolset-2 repository ?

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

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:

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

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

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.

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? >

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

Hi, is there any way to get access to devtoolset-4 ? I see alot of stuff at http://cbs.centos.org/koji/packageinfo?packageID=2076 . Is this not yet released? thanks, Kay

> > 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

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

$ sudo yum install devtoolset-7 Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.vcu.edu * epel: mirror.siena.edu * extras: mirror.vcu.edu * updates: mirror.vcu.edu No package devtoolset-7 available. Error: Nothing to do On Wed, Sep 11, 2019 at 12:17 PM Gordon Messmer <gordon.messmer at gmail.com> wrote: > > On 9/11/19 9:05 AM,

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

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.

On 02/16/2017 09:21 PM, Gordon Messmer wrote: > On 02/16/2017 04:45 PM, Dave Johansen wrote: >> The source RPMs for devtoolset don't appear to be there, but I did find >> them here: >> http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHSCL/SRPMS/ > > > Possibly a result of an unspecified "accident" > >

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 2018-07-05 at 06:16 -0500, Johnny Hughes wrote: > On 07/03/2018 09:04 AM, Sean wrote: > > > <snip> > OK guys .. Firefox 60 is going to take some time .. likely more for > CentOS-6 than CentOS-7. > > They both (C6 and C7 versions) require many non OS tools to build. > > For CentOS-7 .. we need the

Hi! I want to make the default environment for users the environment of devtoolset .. and i am thinking to do it this way: 1. make /bin/bash-devtools with the content scl enable devtoolset-2 bash "$@" 2. change for the prospective users the shell from /bin/bash to /bin/bash-devtoolset Is this the best way? Do anyone see or know of any pitfalls with this? Thanks a lot! Adrian

On 07/06/2018 10:30 AM, Johnny Hughes wrote: > On 07/05/2018 02:27 PM, Phil Wyett wrote: >> On Thu, 2018-07-05 at 06:16 -0500, Johnny Hughes wrote: >>> On 07/03/2018 09:04 AM, Sean wrote: >>>> >> >> >> <snip> >> >>> OK guys .. Firefox 60 is going to take some time .. likely more for >>> CentOS-6 than CentOS-7. >>

Hi! Did anyone tried to use devtoolset from different directory than the default one? from what i can see it would be enough just to change the hardcoded directory in enable file but i would like to hear if someone else tried this ... Thank you! Adrian