[Nix-commits] [NixOS/nixpkgs] 0cac30: racket: disable i686 builds
Branch: refs/heads/release-17.03 Home: https://github.com/NixOS/nixpkgs Commit: 0cac30f5348d371af70aa8d47c778d4cebda2df4 https://github.com/NixOS/nixpkgs/commit/0cac30f5348d371af70aa8d47c778d4cebda2df4 Author: Henry Till Date: 2017-03-05 (Sun, 05 Mar 2017) Changed paths: M pkgs/development/interpreters/racket/default.nix Log Message: --- racket: disable i686 builds ref #23253 (cherry picked from commit 6ed6731e364c68322588b22109208a54747756d3) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] Please test NixOS/nixpkgs.git on darwin
I've updated the wiki with new instructions: https://nixos.org/wiki/Nix_on_OS_X -Henry On Tue, Feb 3, 2015 at 12:52 PM, Daniel Peebles wrote: > > Not much I can think of, but I'm on my phone and can't check now. Perhaps some of our patches to individual packages will affect Linux, and some of those packages might be used by the Linux stdenv bootstrap. Definitely something we should look out for and batch up. > > > > On Feb 3, 2015, at 12:24, Shea Levy wrote: > > Sure, tonight works. This sounds great! Besides the patches to cc-wrapper, are there any changes you expect to hit linux stdenv? > > On Feb 3, 2015, at 5:07 PM, Daniel Peebles wrote: > > I think we can pull it off this or next week, with a few people contributing to testing the semantically meaningful PRs we break into chunks. > > Fully agree on your proposed workflow, but I've been pretty undisciplined so far. For the current big merge, my plan was to break my history into major chunks along the following lines (not necessarily in this order): > - LLVM 3.5 > - Assorted minor Mac-flavored patches to cc-wrapper (hook to detect frameworks in buildInputs, etc.) > - A large collection of source builds for Apple-specific stuff from opensource.apple.com. I've bundled them together in a subdirectory to make it a fairly clean independent PR > - The actual bootstrapped stdenv using clang and my bootstrap tools archive. If there are trust issues with people pulling in my binaries, we can regenerate them, but it'll be a bit of a pain to do sensibly. We should definitely shift the binary bootstrap tools off my Dropbox, either way :) > - A whole load of assorted patches to individual packages to make them work with clang and/or Darwin (should probably be broken up further into smaller categories of breakage being fixed, since there are patterns) > > I think those are the main categories of PR, and I was planning on squashing my messy git history into roughly that shape in the next few days. > > Once we've rewritten that history, I'm quite happy to be more disciplined in my commits to make them merge more easily. > > Want to talk this evening (probably won't be home until 10:30 eastern) on ##nix-Darwin about specifics? I need people to help break out individual parts (e.g., clang) > > Thanks, > Dan > > > On Feb 3, 2015, at 10:13, Shea Levy wrote: > > As far as I know, there is still a lot of churn on pure darwin. > > Dan, if we wanted to merge pure darwin soon (say, maybe this or next week) could you a) get it ready in time and b) adopt a new workflow where future major changes were made and merged in single-feature chunks? I want to avoid a long-term situation where a lot of unconnected changes come in as a set and switch to a feature branch model once pure-darwin is in. > > ~Shea > > On Feb 3, 2015, at 3:03 PM, Wout Mertens wrote: > > Ouch. So users on 10.10 should use Zalora and disable hydra binaries? > > Perhaps we should fast-track the pure-darwin builds. It works swimmingly on my system, and looks like the current Darwin situation is not tenable. So anything in pure-darwin that breaks Linux would be good to find early. > > On Tue Feb 03 2015 at 4:00:48 PM Shea Levy wrote: >> >> I’m not sure about butters. Either way a single cache will not do the trick, as until pure-darwin lands binaries will be specific to the version of OS X they are compiled for. In particular, the zalora cache builds for 10.10. >> >> On Feb 3, 2015, at 2:59 PM, Wout Mertens wrote: >> >> I see that the darwin machine butters is online (and idle) in Hydra, does that mean the zalora cache is no longer needed for nixpkgs on Darwin? >> >> On Tue Feb 03 2015 at 3:51:47 PM Domen Kožar wrote: >>> >>> :beers: >>> >>> On Tue, Feb 3, 2015 at 3:40 PM, Shea Levy wrote: Hi all, For a while now, there has been a lot of work to improve darwin support on the master branch of joelteon’s nixpkgs fork. With the latest staging merge, the core of that work is now on upstream master. The rest of the changes available on joelteon’s fork are very disparate, and it is not clear whether or why they are all needed, so I’d like to request that those who have been working off of the fork test their setups against upstream now. If something is still not working, please at least open an issue, but if you can find the relevant fix on the fork and port it as a PR that would be greatly appreciated. Hopefully we can soon move on from that fork entirely and have further changes (including the ongoing pure-darwin work) done directly against upstream master. Thanks, Shea ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev >>> >>> >>> ___ >>> nix-dev mailing list >>> nix-dev@lists.science.uu.nl >>> http://lists.science.uu.nl/mailman/listinfo/nix-dev >> >> > > > > _
Re: [Nix-dev] Cannot build stdenv-linux-boot on MacOS
Recently, I haven't had any problems with building and SSH keys when doing "nixops deploy" to a VM on OS X after using the setup process outlined in my first email to this thread. -Henry On Sun, Feb 1, 2015 at 2:23 AM, Wout Mertens wrote: > > Note that in order to build packages on the virtual Linux box, you need to be able to ssh to it as root. > Nixops doesn't set that up for nix-build, which is why it fails to build. (this may be a security thing, not sure) > > So once you deployed and it fails to build, do a "nixops ssh" to the Linux vm and set up your own ssh key for root login. > After that, nixops deploy will work even when it needs to build things. > > Wout. > > > On Thu, Jan 29, 2015, 5:31 PM Henry Till wrote: >> >> I should also add that you could just as easily check out the revision of the stable channel if you prefer (currently 676e8d7, found at https://nixos.org/channels/nixos-14.12/). >> >> >> -Henry >> >> >> >> On Thu, Jan 29, 2015 at 11:21 AM, Henry Till wrote: >> > >> > Hello Andreas, >> > >> > It is definitely possible to use NixOps on OS X without a Linux build machine. I've done it recently by installing NixOps directly from Hydra using "nix-install-package", and then using NixOps with a clone of nixpkgs/master in my NIX_PATH (rather than a clone of joelteon/master). >> > >> > Here are some instructions I wrote for doing so: >> > https://gist.github.com/henrytill/ce67b98a5e65452705f5 >> > >> > The only thing I would add to these instructions is that you will get more binaries from cache.nixos.org if you check out your clone of nixpkgs at the same revision as nixos-unstable (currently db75b5d, found at https://nixos.org/channels/nixos-unstable/), and, as a result, "nixops deploy" will be a much quicker process. >> > >> > -Henry >> > >> > >> > >> > On Wed, Jan 28, 2015 at 4:28 PM, Vladimír Čunát wrote: >> > > >> > > Hi. >> > > >> > > On 01/28/2015 08:00 AM, Andreas Bernauer wrote: >> > >> >> > >> error: a ‘x86_64-linux’ is required to build >> > >> ‘/nix/store/6giy9b7xg90p8pqm6f056jqdwdx36jj6-stdenv-linux-boot.drv’, but >> > >> I am a ‘x86_64-darwin’ >> > > >> > > >> > > (Note: I know very little about NixOps, so I may not be accurate.) >> > > You are attempting to build *linux* packages on a darwin machine. You can deploy that way, but you need to add a x86_64-linux machine that will build the stuff (even a virtual one). See http://nixos.org/nix/manual/#chap-distributed-builds >> > > >> > > I don't know if there's a shortcut that also builds on the machines that you deploy to. >> > > >> > > >> > > Vladimir >> > > >> > > >> > > >> > > ___ >> > > nix-dev mailing list >> > > nix-dev@lists.science.uu.nl >> > > http://lists.science.uu.nl/mailman/listinfo/nix-dev >> > > >> >> ___ >> nix-dev mailing list >> nix-dev@lists.science.uu.nl >> http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Cannot build stdenv-linux-boot on MacOS
I should also add that you could just as easily check out the revision of the stable channel if you prefer (currently 676e8d7, found at https://nixos.org/channels/nixos-14.12/). -Henry On Thu, Jan 29, 2015 at 11:21 AM, Henry Till wrote: > > Hello Andreas, > > It is definitely possible to use NixOps on OS X without a Linux build machine. I've done it recently by installing NixOps directly from Hydra using "nix-install-package", and then using NixOps with a clone of nixpkgs/master in my NIX_PATH (rather than a clone of joelteon/master). > > Here are some instructions I wrote for doing so: > https://gist.github.com/henrytill/ce67b98a5e65452705f5 > > The only thing I would add to these instructions is that you will get more binaries from cache.nixos.org if you check out your clone of nixpkgs at the same revision as nixos-unstable (currently db75b5d, found at https://nixos.org/channels/nixos-unstable/), and, as a result, "nixops deploy" will be a much quicker process. > > -Henry > > > > On Wed, Jan 28, 2015 at 4:28 PM, Vladimír Čunát wrote: > > > > Hi. > > > > On 01/28/2015 08:00 AM, Andreas Bernauer wrote: > >> > >> error: a ‘x86_64-linux’ is required to build > >> ‘/nix/store/6giy9b7xg90p8pqm6f056jqdwdx36jj6-stdenv-linux-boot.drv’, but > >> I am a ‘x86_64-darwin’ > > > > > > (Note: I know very little about NixOps, so I may not be accurate.) > > You are attempting to build *linux* packages on a darwin machine. You can deploy that way, but you need to add a x86_64-linux machine that will build the stuff (even a virtual one). See http://nixos.org/nix/manual/#chap-distributed-builds > > > > I don't know if there's a shortcut that also builds on the machines that you deploy to. > > > > > > Vladimir > > > > > > > > ___ > > nix-dev mailing list > > nix-dev@lists.science.uu.nl > > http://lists.science.uu.nl/mailman/listinfo/nix-dev > > ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Cannot build stdenv-linux-boot on MacOS
Hello Andreas, It is definitely possible to use NixOps on OS X without a Linux build machine. I've done it recently by installing NixOps directly from Hydra using "nix-install-package", and then using NixOps with a clone of nixpkgs/master in my NIX_PATH (rather than a clone of joelteon/master). Here are some instructions I wrote for doing so: https://gist.github.com/henrytill/ce67b98a5e65452705f5 The only thing I would add to these instructions is that you will get more binaries from cache.nixos.org if you check out your clone of nixpkgs at the same revision as nixos-unstable (currently db75b5d, found at https://nixos.org/channels/nixos-unstable/), and, as a result, "nixops deploy" will be a much quicker process. -Henry On Wed, Jan 28, 2015 at 4:28 PM, Vladimír Čunát wrote: > > Hi. > > On 01/28/2015 08:00 AM, Andreas Bernauer wrote: >> >> error: a ‘x86_64-linux’ is required to build >> ‘/nix/store/6giy9b7xg90p8pqm6f056jqdwdx36jj6-stdenv-linux-boot.drv’, but >> I am a ‘x86_64-darwin’ > > > (Note: I know very little about NixOps, so I may not be accurate.) > You are attempting to build *linux* packages on a darwin machine. You can deploy that way, but you need to add a x86_64-linux machine that will build the stuff (even a virtual one). See http://nixos.org/nix/manual/#chap-distributed-builds > > I don't know if there's a shortcut that also builds on the machines that you deploy to. > > > Vladimir > > > > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev > ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
