gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11) is a bit old. There have been major changes since then. I'd like a newer version.
If I have to, I expect that I can install from source. I'd rather not.
Is there a CentOS 6-compatible repository from which I can get a newer version? Does a standard CentOS 7 repository have a newer version? Does a CentOS 7-compatible repository have a newer version?
It's my understanding that to compile from source, I will need to keep the gcc I have. Otherwise I would have nothing to compile the source. I expect that providing the right options will let old and new co-exist. Is ensuring that I get the right gcc when I type "gcc" just a matter of having the right search path for gcc? Will I need to do anything interesting to ensure that the resulting executables run using the right libraries?
I've installed from source before, but never to replace an existing compiler. My concern is that if I louse things up, the mess could be very hard to fix.
Take a look at Devtoolset, I think this will give you what you want: https://www.softwarecollections.org/en/scls/rhscl/devtoolset-3/
On Mon, Jun 29, 2015 at 1:56 PM, Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11) is a bit old. There have been major changes since then. I'd like a newer version.
If I have to, I expect that I can install from source. I'd rather not.
Is there a CentOS 6-compatible repository from which I can get a newer version? Does a standard CentOS 7 repository have a newer version? Does a CentOS 7-compatible repository have a newer version?
It's my understanding that to compile from source, I will need to keep the gcc I have. Otherwise I would have nothing to compile the source. I expect that providing the right options will let old and new co-exist. Is ensuring that I get the right gcc when I type "gcc" just a matter of having the right search path for gcc? Will I need to do anything interesting to ensure that the resulting executables run using the right libraries?
I've installed from source before, but never to replace an existing compiler. My concern is that if I louse things up, the mess could be very hard to fix.
-- Michael hennebry@web.cs.ndsu.NoDak.edu "SCSI is NOT magic. There are *fundamental technical reasons* why it is necessary to sacrifice a young goat to your SCSI chain now and then." -- John Woods _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
----- Original Message ----- | Take a look at Devtoolset, I think this will give you what you want: | https://www.softwarecollections.org/en/scls/rhscl/devtoolset-3/ | | | | On Mon, Jun 29, 2015 at 1:56 PM, Michael Hennebry | hennebry@web.cs.ndsu.nodak.edu wrote: | > gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11) is a bit old. | > There have been major changes since then. | > I'd like a newer version. | > | > If I have to, I expect that I can install from source. | > I'd rather not. | > | > Is there a CentOS 6-compatible repository | > from which I can get a newer version? | > Does a standard CentOS 7 repository have a newer version? | > Does a CentOS 7-compatible repository have a newer version? | > | > It's my understanding that to compile from source, | > I will need to keep the gcc I have. | > Otherwise I would have nothing to compile the source. | > I expect that providing the right options will let old and new co-exist. | > Is ensuring that I get the right gcc when I type "gcc" | > just a matter of having the right search path for gcc? | > Will I need to do anything interesting to ensure that | > the resulting executables run using the right libraries? | > | > I've installed from source before, | > but never to replace an existing compiler. | > My concern is that if I louse things up, | > the mess could be very hard to fix. | > | > -- | > Michael hennebry@web.cs.ndsu.NoDak.edu | > "SCSI is NOT magic. There are *fundamental technical | > reasons* why it is necessary to sacrifice a young | > goat to your SCSI chain now and then." -- John Woods
When you're going to maintain software for long periods of time the Modules environment can come in really handy. See http://modules.sf.net
On Jun 29, 2015, at 16:08, James A. Peltier jpeltier@sfu.ca wrote: When you're going to maintain software for long periods of time the Modules environment can come in really handy. See http://modules.sf.net
You can even use modules with the SCL packages, it is a simple translation. Hopefully in the future they will provide native modules.
-- Jonathan Billings
On Mon, 29 Jun 2015, Matt Garman wrote:
Take a look at Devtoolset, I think this will give you what you want: https://www.softwarecollections.org/en/scls/rhscl/devtoolset-3/
Thanks much. It looks like what I want. Also, I think I'll look at the Modules environment in case a convient solution is not available the next time I want to replace a standard package.
-
James A. Peltier -
John R Pierce -
Jonathan Billings -
Matt Garman -
Michael Hennebry