Re: [Nix-dev] gcc has stopped working on Mac OS X Mavericks
Hello nixers, I think I'm having a very similar problem here which I do not have enough nix knowledge to debug. I have reinstalled nix-1.7 doing this (as suggested from the nix website): curl https://nixos.org/nix/install | sh So far so good. But when I try to install ANYTHING, (e.g. hello), this is what I get: installing `hello-2.9' these derivations will be built: /nix/store/al6xyibqncn9aicmkffr0n90xgxnfrm4-hello-2.9.drv building path(s) `/nix/store/71gijbvnnish0gvrci13qpsqxhqwnqvq-hello-2.9' building /nix/store/71gijbvnnish0gvrci13qpsqxhqwnqvq-hello-2.9 unpacking sources unpacking source archive /nix/store/xdilnlzvvsf7r33gs4vy9jq2bmazlc0j-hello-2.9.tar.gz source root is hello-2.9 patching sources configuring configure flags: --disable-dependency-tracking --prefix=/nix/store/71gijbvnnish0gvrci13qpsqxhqwnqvq-hello-2.9 checking for a BSD-compatible install... /nix/store/rc94la2h0pwkshbgmd7kz5nhklkdqyr2-coreutils-8.21/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /nix/store/rc94la2h0pwkshbgmd7kz5nhklkdqyr2-coreutils-8.21/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for gcc... gcc checking whether the C compiler works... no configure: error: in `/private/var/folders/js/cv_q5mqd6_g76353vq_n4nqcgn/T/nix-build-hello-2.9.drv-0/hello-2.9': configure: error: C compiler cannot create executables See `config.log' for more details builder for `/nix/store/al6xyibqncn9aicmkffr0n90xgxnfrm4-hello-2.9.drv' failed with exit code 77 error: build of `/nix/store/al6xyibqncn9aicmkffr0n90xgxnfrm4-hello-2.9.drv' failed -- Which makes me suspect the error is very similar. Likewise, my xcrun thinks I'm on 10.10. I have seen mentioned as workaround to export that environment variable inside pkgs/stdenv/nix/default.nix: I have tried both extraCmd and shellHooks inside stdenvNix, but with no luck. My nix-expression knowledge stops here unfortunately :( Any kind soul keen on helping? Thanks! Alfredo On 25 October 2014 04:17, John Wiegley jo...@newartisans.com wrote: Michael Sperber sper...@deinprogramm.de writes: That setting didn't take for me. But your hint made me set SDKROOT in pkgs/stdenv/nix/default.nix directly, and that did the trick. I had to set this: export SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk John ___ 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] Zero Hydra Failures (ZHF) project for NixOS
This is all becoming too restrictive. I think merge the PR and go on. If it just doesn't work, revert. If it e.g. builds on linux and not on darwin, just remove from platforms. I'd please everybody to not put too bureaucracy in the process. Keeping hydra to zero is frustrating, as well as accumulating pull requests and letting other people keep branches and branches of branches around. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] system wide .vimrc / managing plugins the nix way - proposal and implementation
Well - it might be desirable - but for other users vim should be the way
they know it - plain simple stupid. Thus forcing a customized vim
behavior on other people is could be a pain.
The first step for letting the users choose is
- create nix code creating .vimrc files
- create vim wrappers which use them, eventually having a different name
This patch implements this:
http://mawercer.de/tmp/vim-patch
More than that VAM (vim-addon-manager) got a autoload/nix.vim file which
can turn github based plugins (known by vim-pi) into nix derivations.
I'm not sure I should call myself of being a maintainer of anything
within nix, its just what I think will provide greatest value with least
effort. This change was driven by the discussion found here:
https://github.com/jagajaga/nixpkgs/commit/0b9432d5e22fc5453e0b4265ca36d5015cbcaf1c#commitcomment-8305911
The perfect fix (creating a huge package cross language/tool packagce
database) would be a lot more work, putting all vim plugins into nixpkgs
( 5.000 - a lot are no longer used) would be overkill. Thus this
attempt tries to follow the cabal2nix like approach making packaging
plugins people use easier while supporting enhancements such as
addon-info.json files introduced by VAM containing simple unversioned
dependency information.
The result looks like this illustrating how much the unversioned
dependency management of VAM can simplify your setup:
# test cases:
test_vim_with_vim_addon_nix_using_vam = vim_configurable.customize {
name = vim-with-vim-addon-nix-using-vam;
vimrcConfig.vam.plugins = [
{name = vim-addon-nix; }
];
};
test_vim_with_vim_addon_nix_using_pathogen = vim_configurable.customize {
name = vim-with-vim-addon-nix-using-pathogen;
vimrcConfig.pathogen.plugins = map (x: vimPlugins.${x}) [
# target package:
vim-addon-nix
# dependencies:
vim-addon-completion vim-addon-goto-thing-at-cursor
vim-addon-mw-utils vim-addon-actions vim-addon-errorformats tlib
];
};
The depeendency magic is provided by a dependencies = [name1 name2]
attr in vimPlugins.
Please note that all features provided by VAM's vam#Scripts() function
are supported such as loading plugins lazily triggered by you opening
some special particular filetype.
Because pathogen and VAM are supported (sorry no Vundle/ NeoBundel
support yet) this should please the majority. Pathogen has no advantage
over VAM AFAIK - I just added it for completness and because the
discussion mentioned above asked for it.
This mail is for gathering feedback, I'll create a pull request soon.
Marc Weber
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] perl-devel-repl: REPL for Perl
Below is a link to a patch for the Devel::REPL Perl module and some dependencies. Devel::REPL includes re.pl, a REPL for Perl. https://pastee.org/c6mw [1] Seems to work a bit better when used with perlPackages.TermReadLineGNU. Cheers [1] Sorry it's a link but haven't figured out how to post patches via gmane's web interface without them getting mangled. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
