Update to gcc 4.7 #237

Closed
viric opened this Issue Dec 30, 2012 · 15 comments

Projects

None yet

5 participants

@viric
Member
viric commented Dec 30, 2012

Even if we don't do that for this stdenv-updates (I'd like to), we could test at least a branch with that.

The branch is already at https://github.com/NixOS/nixpkgs/tree/stdenv-updates-gcc47

Now it'd be nice for hydra people to set up testing for this.

@viric
Member
viric commented Dec 30, 2012

I think that gcc 4.7 has much better gdwarf4 support, which I'd like to use in my system when debugging things.

I've also been told that gcc until 4.7.2 has important issues for the mips platform. I've had some kernels built in 4.6 not booting, I think related to this. I've no solid proof though.

@peti
Member
peti commented Jan 11, 2013

+1

I, too, would like to see Nixpkgs update to GCC 4.7.x by default.

@peti
Member
peti commented Jan 12, 2013

nix-build <nixos> -A system succeeds fine in both the stdenv-updates and the stdenv-updates-gcc47 branch.

@viric
Member
viric commented Jan 12, 2013

Yes, I've used gcc47 to bootstrap some systems, and all worked fine, but some packages, that required '-fpermissive' mainly.

@peti
Member
peti commented Jan 21, 2013

Could we merge stdenv-updates-gcc47 into the normal stdenv-updates branch? Does anyone see a reason why those two branches should remain separate?

@vcunat
Member
vcunat commented Jan 21, 2013

I also wondered about that. Certainly they should be merged before merging either into master.

@viric
Member
viric commented Jan 21, 2013

On Mon, Jan 21, 2013 at 02:26:18AM -0800, Vladimír Čunát wrote:

I also wondered about that. Certainly they should be merged before merging either into master.

The main reason is that niksnut didn't want gcc 4.7 in stdenv-updates. But I
created this branch to push into the direction of getting it into
stdenv-updates.

I asked for the gcc47 branch to be tested by hydra, but that also hasn't
happened.

@peti
Member
peti commented Jan 21, 2013

Let's agitate on the -dev mailing list. :-)

@rbvermaa
Member

I told viric on IRC that a jobset for it on hydra.nixos.org is fine, as long as it starts off with a smaller subset of nixpkgs.

@vcunat
Member
vcunat commented Jan 21, 2013

It seems that gcc-4.7 is quite well supported now and we should get almost everything to build, perhaps with a little work. Packages that won't work could be build temporarily with an older version, we've got nix don't we :-)

Fedora uses it since 17 and in Gentoo the list of problems is quite short https://bugs.gentoo.org/show_bug.cgi?id=gcc-4.7 ... so there will be sources in which we can find solutions to the problems.

Example motivation (from http://gcc.gnu.org/gcc-4.7/changes.html): LTO improvements

The serial stage of linking Firefox has been sped up by about a factor of 10.

@rbvermaa: merging the two testing branches would solve the double-building overhead

@viric
Member
viric commented Jan 21, 2013

On Mon, Jan 21, 2013 at 02:45:26AM -0800, Rob Vermaas wrote:

I told viric on IRC that a jobset for it on hydra.nixos.org is fine, as long as it starts off with a smaller subset of nixpkgs.

Yes, I remember, but I don't know how to create that jobset. :)

@rbvermaa
Member

You request it at either me or Eelco, telling us what is the branch name, purpose of the branch, and the release.nix expression that should be used (which has the smaller subset in it).

@viric
Member
viric commented Jan 21, 2013

On Mon, Jan 21, 2013 at 03:08:45AM -0800, Rob Vermaas wrote:

You request it at either me or niksnut, telling us what is the branch name, purpose of the branch, and the release.nix expression that should be used (which has the smaller subset in it).

Ah ok, well I think I already considered it 'requested'. :) Nevertheless, I
don't think it will be very useful, if it's without the full packages. Niksnut
concerns were about having some packages not building, and we should detect
them.

A small subset would tell that gcc47 doesn't fail directly; but I think it
should work quite enough already.

In short, I don't think a small subset would be useful, in terms of making
niksnut accept gcc 4.7.

@shlevy
Member
shlevy commented Mar 9, 2013

Can we merge the gcc-4.7 branch into stdenv-updates now?

@vcunat
Member
vcunat commented Mar 9, 2013

I merged it now. Issues about it probably belong to another thread already.

@vcunat vcunat closed this Mar 9, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment