Hi Eelco,
> Well, GCC updates tend to break many packages, so this will delay a
> stdenv-updates merge even further. I would prefer merging
> stdenv-updates into master first (to get the latest Glibc, and some
> other stuff) and do GCC 4.7 after that.
could we build the stdenv-updates-gcc47 b
Hi.
On 01/21/2013 12:42 PM, Eelco Dolstra wrote:
Well, GCC updates tend to break many packages, so this will delay a
stdenv-updates merge even further. I would prefer merging stdenv-updates into
master first (to get the latest Glibc, and some other stuff) and do GCC 4.7
after that.
Nice solut
Hi,
On 21/01/13 11:49, Peter Simons wrote:
> there are some who would like to have gcc 4.7.x as default compiler in
> Nixpks (see issue #237 on Github). We have a working configuration in
> 'stdenv-updates-gcc47' that has proven quite stable. I'd like to suggest
> that we merge those updates into
Hi,
there are some who would like to have gcc 4.7.x as default compiler in
Nixpks (see issue #237 on Github). We have a working configuration in
'stdenv-updates-gcc47' that has proven quite stable. I'd like to suggest
that we merge those updates into the normal 'stdenv-updates' branch, so
that we
