[closed-case] Any way to use an older GCC toolchain with makepkg?

headkase · 2012-04-15 01:37:02

I'm having issues with a package in AUR: Code::Blocks SVN.

I'm writing this question in Newbie Corner because it is a general question with that particular PKGBUILD being a case of it.

Anyway, I'm running into compilation issues. I believe if I could use an older version of g++, say 4.6.3 instead of 4.7.0, that the compilation would succeed. My question: is it possible to have side-by-side GCC installs and how would I specify, perhaps in /etc/makepkg.conf, which to use for a PKGBUILD?

Edit:
Here is a thread on Code::Blocks own forums which highlights that GCC 4.7.0 has compilation issues with C::B.

Last edited by headkase (2012-04-16 07:13:39)

KingX · 2012-04-15 05:22:53

I think it would be better to wait for a work-around/patch of some sort to show up. Two gcc version's side-by-side will be messy i think. Did you try the workaround mentioned in the first post "This can be temporarily worked around by using -fpermissive"?

ConnorBehan · 2012-04-15 06:03:09

I agree with KingX, but if you must use an older version there's gcc41 through gcc45 in the AUR. It looks like they handle conflicts by configuring with --program-suffix=whatever.

headkase · 2012-04-15 17:54:47

KingX, -fpermissive allows the compilation to go much further but it still errors out.

ConnorBehan, I'll look into the AUR GCC's - I don't know if I'll try it yet but thank you for pointing them out for me: I searched the official packages and only saw GCC 4.7.0 and forgot to search AUR..

headkase · 2012-04-16 06:20:06

Apparently, after much googling: lots of projects have trouble compiling with GCC 4.7.0. It's not limited just to Code::Blocks. I don't know about you but to me this would seem to be an issue, more-so to Arch as it is rolling release than to other distro's which may stick to older compilers longer, from a development perspective. It might even rise to the level where Arch could have say GCC 4.6.x lts, GCC 4.5.x lts, and so on. Then in makepkg.conf a variable to specify which compiler toolchain to use. I know all developers should be updating their source-code to GCC 4.7.0 but, you just know, that's not going to happen for everything.

Allan · 2012-04-16 06:27:15

headkase wrote:

It might even rise to the level where Arch could have say GCC 4.6.x lts, GCC 4.5.x lts, and so on. Then in makepkg.conf a variable to specify which compiler toolchain to use.

Never going to happen.

headkase · 2012-04-16 06:51:25

Allan wrote:

headkase wrote:
It might even rise to the level where Arch could have say GCC 4.6.x lts, GCC 4.5.x lts, and so on. Then in makepkg.conf a variable to specify which compiler toolchain to use.
Never going to happen.

Okey-doke.

Mr.Elendig · 2012-04-16 07:03:15

Install gcc46 or whatever you want from aur, export CC=path/to/gcc4.6binary. Same with CXX

headkase · 2012-04-16 07:10:46

Mr.Elendig wrote:

Install gcc46 or whatever you want from aur, export CC=path/to/gcc4.6binary. Same with CXX

The most recent non-cross-compiling GCC in AUR is GCC45. It's an orphan and the latest comment in it says the build is broken.

Thank you though, I've decided to wait for a patch - that is the most reasonable thing all around. However, there is a "gcc 4.7.0 broken" thread on Code::Blocks forums so I believe I'll post there as well - eventually, hopefully, the C::B SVN will Just Work™ on Arch

I'll mark this thread as closed-case, not because it is solved but because it has been fully considered.

Edit: originally edited title to "closed" but then realized that has forum-meaning so re-edited to "closed-case"

Last edited by headkase (2012-04-16 07:14:45)

Mr.Elendig · 2012-04-16 07:19:04

headkase wrote:

The most recent non-cross-compiling GCC in AUR is GCC45. It's an orphan and the latest comment in it says the build is broken.

Easy to fix. Make a new one for gcc46 while you are at it. You can just rip off the 4.6.x PKGBUILD in abs and just change the install paths and binary name.

headkase · 2012-04-16 07:26:39

Thanks again, I'll think about it and also look into it a bit - if I think I can do it, within my current ability, then I just might!

Arch Linux

#1 2012-04-15 01:37:02

[closed-case] Any way to use an older GCC toolchain with makepkg?

#2 2012-04-15 05:22:53

Re: [closed-case] Any way to use an older GCC toolchain with makepkg?

#3 2012-04-15 06:03:09

Re: [closed-case] Any way to use an older GCC toolchain with makepkg?

#4 2012-04-15 17:54:47

Re: [closed-case] Any way to use an older GCC toolchain with makepkg?

#5 2012-04-16 06:20:06

Re: [closed-case] Any way to use an older GCC toolchain with makepkg?

#6 2012-04-16 06:27:15

Re: [closed-case] Any way to use an older GCC toolchain with makepkg?

#7 2012-04-16 06:51:25

Re: [closed-case] Any way to use an older GCC toolchain with makepkg?

#8 2012-04-16 07:03:15

Re: [closed-case] Any way to use an older GCC toolchain with makepkg?

#9 2012-04-16 07:10:46

Re: [closed-case] Any way to use an older GCC toolchain with makepkg?

#10 2012-04-16 07:19:04

Re: [closed-case] Any way to use an older GCC toolchain with makepkg?

#11 2012-04-16 07:26:39

Re: [closed-case] Any way to use an older GCC toolchain with makepkg?

Board footer