[opensuse] Updating gcc to 4.9 or 5 from devel with 13.1 - Any gotchas?
All, There are some C11 additions made in 4.9 (_Generic, etc..) that are not available in 13.1 with gcc 4.8 (or 13.2 if gcc 4.8 was used). gcc 4.9 and 5 are available in the devel:/gcc repo. I am going to update, but before I do I thought I would check with the list and see if that update has any unintended side effects, dkms issues for module rebuilds, etc. I don't see any issues that I would expect, whatever calls gcc will get gcc, but not knowing if anything release related is tied to the /usr/lib64/... path for 4.8 specifically, or will require massive rebuild of software after install of the newer version is the concern. Anybody running 13.1 moved to gcc 4.9 or later? Any problems? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-04-17 07:14, David C. Rankin wrote:
All,
There are some C11 additions made in 4.9 (_Generic, etc..) that are not available in 13.1 with gcc 4.8 (or 13.2 if gcc 4.8 was used). gcc 4.9 and 5 are available in the devel:/gcc repo. I am going to update, but before I do I thought I would check with the list and see if that update has any unintended side effects,
I believe the trick is to have both installed, with the old one as default. But I don't remember how this is done. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/17/2016 06:50 AM, Carlos E. R. wrote:
On 2016-04-17 07:14, David C. Rankin wrote:
All,
There are some C11 additions made in 4.9 (_Generic, etc..) that are not available in 13.1 with gcc 4.8 (or 13.2 if gcc 4.8 was used). gcc 4.9 and 5 are available in the devel:/gcc repo. I am going to update, but before I do I thought I would check with the list and see if that update has any unintended side effects,
I believe the trick is to have both installed, with the old one as default. But I don't remember how this is done.
Thanks Carlos, I haven't been able to find a specific, but I have this nagging feeling that if I replace the default gcc, really bad things will happen. I can't remember when or where this discussion was had before, but sometime in the past 15 years I remember there being advise against a wholesale change of gcc version on SuSE. I'll skip the upgrade for now and just use another box when I run into these issues. Anybody else have any thoughts here, just let me know. Thanks. - -- David C. Rankin, J.D.,P.E. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlca1HAACgkQZMpuZ8CyrcjcGACcCFp576cT9sDDD+04Jf5LVfif 464An3XkufFped4Wb6zaD7yA2scww7VB =PP6f -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Apr 22, 2016 at 9:48 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/17/2016 06:50 AM, Carlos E. R. wrote:
On 2016-04-17 07:14, David C. Rankin wrote:
All,
There are some C11 additions made in 4.9 (_Generic, etc..) that are not available in 13.1 with gcc 4.8 (or 13.2 if gcc 4.8 was used). gcc 4.9 and 5 are available in the devel:/gcc repo. I am going to update, but before I do I thought I would check with the list and see if that update has any unintended side effects,
I believe the trick is to have both installed, with the old one as default. But I don't remember how this is done.
Thanks Carlos,
I haven't been able to find a specific, but I have this nagging feeling that if I replace the default gcc, really bad things will happen. I can't remember when or where this discussion was had before, but sometime in the past 15 years I remember there being advise against a wholesale change of gcc version on SuSE. I'll skip the upgrade for now and just use another box when I run into these issues.
Anybody else have any thoughts here, just let me know. Thanks.
Adding a new GCC as a non-default compiler on the system should be safe. Like Carlos, I don't know how to do that. For the default compiler, I know it is typically a multi-month process to update GCC in factory. There is a GCC 6 staging project right now where they are working out the next update. https://build.opensuse.org/project/monitor/openSUSE:Factory:Staging:Gcc6 Note that GCC 6 is already in factory as an optional compiler: https://build.opensuse.org/package/show/openSUSE:Factory/gcc6 It is making it the default that is a much bigger task. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi David, * David C. Rankin (drankinatty@suddenlinkmail.com) [20160423 03:48]:
I haven't been able to find a specific, but I have this nagging feeling that if I replace the default gcc,
/usr/bin/gcc is just a symlink to the gcc binary, e.g. gcc-4.8. AFAIK the packages in devel:gcc don't come with that symlink. But even if they did, you could just change the symlink. All other version specific files are in a versioned directory below /<libdir>/gcc/<target_arch>/<version> ( e.g. /usr/lib64/gcc/x86_64-suse-linux/6 ) so they don't mix. To use the other gcc versions, just call gcc-4.9 or gcc-5.0 (i.e. doing CC=gcc-4.9 make ...). hth Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R. -
David C. Rankin -
Greg Freemyer -
Philipp Thomas