Hi Konrad, Konrad Hinsen <[email protected]> skribis:
> --On 17 avril 2012 14:25:18 +0200 Ludovic Courtès > <[email protected]> wrote: > >> It turns out that getting GCC 4.6 to build on Darwin wasn’t so >> difficult. The patch below fixes that, by adding lipo(1) to stdenv. >> However, since it modifies stdenv, it entails a full rebuild. >> >> Would it be a problem for you? What do others think? > > I don't mind any rebuild, as long as the result works. It's done only > once, after all. Good. :-) > Which builder.sh is the patch for? Is it > pkgs/development/compilers/gcc/4.6/builder.sh? No, stdenv. >> Besides, having a working GCC on MacOS X raises the question of whether >> its stdenv should be use it in lieu of Apple’s GCC 4.2 (which is old, >> buggy, and no longer maintained.) I’m inclined to stick to Apple’s >> GCC for now, because it’s good for portability testing. But we could >> still switch in the future. > > I'd argue for gcc 4.6, for compatibility with the rest of the world. I > expect to use Nixpkgs like I use MacPorts now: for building standard > Unix stuff. For programs written explicitly for the Mac, I usually > install prebuilt binaries like most users do, again for compatibility > with what most users do. OK. The use case I had in mind was continuous integration with Hydra on MacOS: in that case one often typically wants something that closely resembles a “normal” MacOS X. Thanks, Ludo’. _______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
