gcc-4.5.0 question

wrc1944 · 2010-04-16 19:50:52

I just noticed on my weekly "pacman -Syu" that gcc-4.5.0-1-x86_64 is in the updates, so I assume all the other packages in that repo have been compiled with gcc-4.5.0.

I mentioned this on the Gentoo gcc-4.5 "unsupported software" forum, and a dev said he thinks not.

I wouldn't make such assumptions... I bet most, if not all, the packages in the repo are still compiled with GCC 4.4.x or some even GCC 4.3.x still. Such mass-rebuilds are not required for most GCC updates.

Could an Arch dev or someone who knows please comment on this? I'd sure like to know if my Arch "testing" pre-compiled binary installation is now being compiled with gcc-4.5.0.

I use to compile Arch, but doing that and Gentoo is simply too much compiling on a little under-powered system- just takes too much time, so I currently use the Arch repos.

Allan · 2010-04-16 22:14:12

New packages will be compiled with it, but we do no rebuild the entire distro for a gcc update.

wrc1944 · 2010-07-25 20:13:20

It's been 3+ months now, so after many,many pacman -Syu's, can I pretty much assume most of my Arch "testing" binaries system is now compiled with gcc-4.5.0?

I haven't counted the packages, but I know it's been hundreds and hundreds of updates during this time. Does "new packages" Allan mentions mean all installed and then updated packages are considered as "new," or does it refer to a package not previously installed being installed for the first time?

Ranguvar · 2010-07-25 20:26:39

Do a 'pacman -Qi' on any package you like, then check the build date.
If it's after gcc 4.5.0 was added, then yeah, it's probably been compiled with 4.5.

wrc, new packages includes updates, because when a new version is uploaded, it obviously must be compiled again

wrc1944 · 2010-07-26 03:06:55

Thanks much Ranguvar,
Good knowing that. Maybe you or someone else could answer a question about how Arch uses gcc-4.5.0.

I'd be interested in what CFLAGS and CXXFLAGS/LDFLAGS are used by gcc in compiling the Arch Linux packages (or how I could find out), as it's apparently working.

I run 4 different Gentoo testing installs, and decided to try and move one of them (an amd64 install) to gcc-4.5.0, which is still masked in Gentoo testing portage. I could use an overlay with layman, but I chose to unmask the portage version, and ran into problems. I could build gcc-4.5.0 OK using gcc-4.4.4, but then ran into trouble when trying to first rebuild the toolchain with 4.5.0, even with a bare set of cflags, and without the -flto and -ftree-vectorize flags. Failed on libtool, which apparently is a known problem with -flto, among others, and on my system even without -flto.

Thought I might pick up some clues and more info by looking over how Arch manages to compile packages with gcc-4.5.0. Where should I look for the global cflag settings?

Or, does Arch have per package settings ans perhaps gcc-4.5.0 patches not in the Gentoo portage or overlay ebuilds? Not sure, as I've only run Arch testing with the pre-compiled binaries.

Allan · 2010-07-26 03:39:16

For CFLAGS/CXFLAGS/LDFLAGS look in /etc/makepkg.conf.

Also, I have had to do a lot of patching to get gcc-4.5.0 in the shape it is in now. We use the 20100610 snapshot with a couple more backported fixes.

Arch Linux

#1 2010-04-16 19:50:52

gcc-4.5.0 question

#2 2010-04-16 22:14:12

Re: gcc-4.5.0 question

#3 2010-07-25 20:13:20

Re: gcc-4.5.0 question

#4 2010-07-25 20:26:39

Re: gcc-4.5.0 question

#5 2010-07-26 03:06:55

Re: gcc-4.5.0 question

#6 2010-07-26 03:39:16

Re: gcc-4.5.0 question

Board footer