Re: [Nix-dev] Force Hydra to use localhost for building

2014-11-12 Thread Peter Simons
Hi Nikolay,,

 > Unfortunately, with distributed build enabled Hydra doesn't use its
 > own server for building at all.

it does, but only if all remote machines are busy. If you have build
slaves with a configured maximum capacity of n jobs, then the n+1-th
parallel build job (and all beyond that) will run on localhost.

It's an imperfect situation.

Best regards,
Peter

___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Vim conceal, cscope and other features

2014-11-12 Thread Andreas Herrmann
Hi,

> Is there an easy way to
> enable them (I know I can copy the nix file and edit it to my hearts
> content, but I was hoping there is a better way)?

You could use `overrideDerivation` and hotfix the configureFlags. Grep for it 
in nixpkgs/pkgs to see a few example. 

There is an instructive one in pkgs/servers/x11/xorg/overrides.nix

  let  inherit (lib) overrideDerivation; in
  # ...
  darwinOtherX = overrideDerivation xorgserver (oldAttrs: {
# ...
configureFlags = oldAttrs.configureFlags ++ [
  "--disable-xquartz"
  "--enable-xorg"
  "--enable-xvfb"
  "--enable-xnest"
  "--enable-kdrive"
];
# ...
  });

Best, Andreas


On Wednesday 12 November 2014 00:17:07 Richard Wallace wrote:
> Hey all,
> 
> I just realized that vim in nix isn't configured with the conceal and
> cscope features enabled.   Any reason for that? Is there an easy way to
> enable them (I know I can copy the nix file and edit it to my hearts
> content, but I was hoping there is a better way)?
> 
> Thanks,
> Rich
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Travis false-positives

2014-11-12 Thread Georges Dubus
Hi Peter

I started working with travis because there was already some low quality
patches that broke evaluation when merged. Hopefully, this kind of bad
patches don't get merged anymore.

However, what you describe is indeed a problem. I'll see what I can do to
inform contributor of actual role of travis, and what to expect from it.

George

Georges Dubus

2014-11-08 0:24 GMT+01:00 Peter Simons :

> Hi Georges,
>
>  > I think of it more as proof of concept of what CI on the pull
>  > requests can bring us than a final testing workflow.
>
> unfortunately, users submitting pull requests cannot see that the
> travis-ci job isn't supposed to be considered "reliable". I've run into
> cases where people submit totally untested patches as a PR, because they
> assume travis-ci will test the patch for them. Travis, however, comes
> back with some kind of system failure that gives no indication whether
> the patch is good or not.
>
> This means that users are more likely to submit broken patches because
> they rely on a safety net that actually doesn't exist. Because of this
> phenomenon, the travis-ci job actually decreases the quality of our
> submissions!
>
> Is it possible to add a note to the PR status pages that draws people's
> attention to the fact that the travis-ci service is experimental?
>
> Best regards,
> Peter
>
> ___
> 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] Introducing nox and nox-review

2014-11-12 Thread Georges Dubus
Hello everyone.

I just realized I've never properly announced nox on the mailing list, so
here it comes.

I'm happy to present the nox tools suite, which is a set of tools designed
to improve the use of Nix and NixOS. The code can be found at
https://github.com/madjar/nox, and nox is available in nixpkgs as the "nox"
attribute. There are already two tools that should make your life easier.

"nox" itself is a command line tool that help you search nixpkgs to install
packages. It's basically a nicer version of the old "nix-env -qaP | grep",
with caching to make search faster, color, and a few other niceties.

"nox-review" is a tool designed to help those who work on nixpkgs.
"nox-review pr PR_NUMBER" downloads a pull request, merges it in master,
and build every single path affected by the pull request (each package
changed by the pr, and all their dependencies). This makes it easy for a
reviewer to build a pull request before merging it, and allow them to make
sure that nothing unexpected was broken by a pull request. "nox-review
wip", on the other hand, can be used to make sure the changes introduced in
a nixpkgs working tree don't break anything.


I hope you can make a good use of those tools, especially "nox-review pr"
which I hope can improve the reliability of nixpkgs by making it easier to
catch breakage early.

Cheers
--
Georges
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Introducing nox and nox-review

2014-11-12 Thread Damien Cassou
Hi,

On Wed, Nov 12, 2014 at 1:46 PM, Georges Dubus  wrote:
> I just realized I've never properly announced nox on the mailing list, so
> here it comes.

I wrote a simple nixos-update script that might also be useful to some
users. Its comment is:

# Update ~/nixpkgs git repository based on what is the latest nixos unstable:
# - the git 'basesystem' branch is the branch always pointing to nixos unstable
# - the git 'system' branch is based on 'basesystem' and adds my own
stuff on top

the code can be found at
https://gist.github.com/DamienCassou/bce633bba3eb1dfada1f

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Introducing nox and nox-review

2014-11-12 Thread Marc Weber
https://nixos.org/wiki/Howto_find_a_package_in_NixOS
is the place to add a reference..

Marc Weber
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Introducing nox and nox-review

2014-11-12 Thread member MP2E
Thank you for posting this! I was not aware such utilities existed, but it
will make managing pull requests much easier for me from here on out

On Wed, Nov 12, 2014 at 5:11 AM, Damien Cassou 
wrote:

> Hi,
>
> On Wed, Nov 12, 2014 at 1:46 PM, Georges Dubus 
> wrote:
> > I just realized I've never properly announced nox on the mailing list, so
> > here it comes.
>
> I wrote a simple nixos-update script that might also be useful to some
> users. Its comment is:
>
> # Update ~/nixpkgs git repository based on what is the latest nixos
> unstable:
> # - the git 'basesystem' branch is the branch always pointing to nixos
> unstable
> # - the git 'system' branch is based on 'basesystem' and adds my own
> stuff on top
>
> the code can be found at
> https://gist.github.com/DamienCassou/bce633bba3eb1dfada1f
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Success is the ability to go from one failure to another without
> losing enthusiasm."
> Winston Churchill
> ___
> 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] clang-based stdenv for OSX Yosemite

2014-11-12 Thread Wout Mertens
So on a fresh 10.10 with XCode 6.1 the joelteon master branch can't build
things like Python. The error is below, I presume it is because the
downloaded clang depends on libraries that aren't available. Should I just
rebuild the world without binary cache?

configure:3947: checking whether the C compiler works

configure:3969: clang
-I/nix/store/0vxclyfimw81d5a42z5awxmkvl3zgl1x-zlib-1.2.8/include
-I/nix/store/0x4dqky1g3jvwvadcw51najjj0a6ibiq-bzip2-1.0.6/include
-I/nix/store/0zma7049nw3mwq8aik183i2mbpgw2426-xz-5.0.5/include
-I/nix/store/i49hpms5d8j0cg2izjxnzyl9b02s508j-gdbm-1.11/include
-I/nix/store/z1sh0nlnwlv0yma6c91m55fq9zr9d9fa-sqlite-3.8.7/include
-I/nix/store/igmjzlrkczlzggaplyi3makxfm9iqvkg-db-5.3.28/include
-I/nix/store/m8gw7ggzdny8p2w9dik9f481pmjwmpma-readline-6.3p08/include
-I/nix/store/fc688jhpqkbjxhn8xnksswpv5szcvdxg-ncurses-5.9/include
-I/nix/store/89zxnpdrhv2z9lffhhmjac52dspqqpi4-openssl-1.0.1j/include
-I/nix/store/rah8sp90y0aml9495av4w6ls3y7vjdnj-tcl-8.5.15/include
-I/nix/store/7yhp7w16wnq206x4qih2fzfkkbm7s558-tk-8.5.15/include
-I/nix/store/kpfyi3q82iblsnb663ybksnas5g09x3q-libX11-1.6.2/include
-I/nix/store/wxv9vgqi60dhxm33q10lh0wx8p8l1glk-xproto-7.0.26/include
-L/nix/store/0vxclyfimw81d5a42z5awxmkvl3zgl1x-zlib-1.2.8/lib
-L/nix/store/0x4dqky1g3jvwvadcw51najjj0a6ibiq-bzip2-1.0.6/lib
-L/nix/store/0zma7049nw3mwq8aik183i2mbpgw2426-xz-5.0.5/lib
-L/nix/store/i49hpms5d8j0cg2izjxnzyl9b02s508j-gdbm-1.11/lib
-L/nix/store/z1sh0nlnwlv0yma6c91m55fq9zr9d9fa-sqlite-3.8.7/lib
-L/nix/store/igmjzlrkczlzggaplyi3makxfm9iqvkg-db-5.3.28/lib
-L/nix/store/m8gw7ggzdny8p2w9dik9f481pmjwmpma-readline-6.3p08/lib
-L/nix/store/fc688jhpqkbjxhn8xnksswpv5szcvdxg-ncurses-5.9/lib
-L/nix/store/89zxnpdrhv2z9lffhhmjac52dspqqpi4-openssl-1.0.1j/lib
-L/nix/store/rah8sp90y0aml9495av4w6ls3y7vjdnj-tcl-8.5.15/lib
-L/nix/store/7yhp7w16wnq206x4qih2fzfkkbm7s558-tk-8.5.15/lib
-L/nix/store/kpfyi3q82iblsnb663ybksnas5g09x3q-libX11-1.6.2/lib
-L/nix/store/wxv9vgqi60dhxm33q10lh0wx8p8l1glk-xproto-7.0.26/lib conftest.c
-lncurses >&5

ld: library not found for -lcrt1.10.6.o

clang-3.5: error: linker command failed with exit code 1 (use -v to see
invocation)

On Fri Nov 07 2014 at 6:23:57 PM Eric Seidel  wrote:

> Alfredo Di Napoli  writes:
>
> > Thank you so much guys for your stoic effort!
> > For the nix newbies like me, could you please expand upon
> > "If you would like to use our branch you should add hydra.joelt.io to
> your
> > binary caches."
>
> You want to set the binary-caches option in nix.conf, e.g.
>
>   binary-caches = http://cache.nixos.org http://hydra.joelt.io
>
> I think nix looks for /etc/nix/nix.conf by default, but this is
> configurable via the NIX_CONF_DIR environment variable.
>
> Eric
> ___
> 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] Vim conceal, cscope and other features

2014-11-12 Thread Vladimír Čunát

Hi.

On 11/12/2014 10:53 AM, Andreas Herrmann wrote:

You could use `overrideDerivation` and hotfix the configureFlags. Grep for it 
in nixpkgs/pkgs to see a few example.


That's an overkill. vim_configurable uses your ~/.nixpkgs/config.nix 
file. Basic idea is like this

https://nixos.org/wiki/Enable_Browser_Plugins ,
the list of configurable options (this way):
https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/editors/vim/configurable.nix#L135

Vladimir




smime.p7s
Description: S/MIME Cryptographic Signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Vim conceal, cscope and other features

2014-11-12 Thread Richard Wallace
That's exactly what I was looking for, thanks!

On Wed, Nov 12, 2014 at 8:15 AM, kickmymotorcy...@gmail.com <
kickmymotorcy...@gmail.com> wrote:

> Rich,
>
> If you install the package `vimHugeX` instead of `vim`, you get a
> bunch of other features, including cscope and conceal.
>
> Here's the output of `vim --version` for the vimHugeX package:
>
> $ vim --version
> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Oct 21 2014 02:43:02)
> Included patches: 1-335
> Compiled by nixbld
> Huge version with GTK2 GUI.  Features included (+) or not (-):
> +acl +farsi   +mouse_netterm   +syntax
> +arabic  +file_in_path+mouse_sgr   +tag_binary
> +autocmd +find_in_path-mouse_sysmouse  +tag_old_static
> +balloon_eval+float   +mouse_urxvt -tag_any_white
> +browse  +folding +mouse_xterm -tcl
> ++builtin_terms  -footer  +multi_byte  +terminfo
> +byte_offset +fork()  +multi_lang  +termresponse
> +cindent -gettext -mzscheme+textobjects
> +clientserver-hangul_input+netbeans_intg   +title
> +clipboard   +iconv   +path_extra  +toolbar
> +cmdline_compl   +insert_expand   -perl+user_commands
> +cmdline_hist+jumplist+persistent_undo +vertsplit
> +cmdline_info+keymap  +postscript  +virtualedit
> +comments+langmap +printer +visual
> +conceal +libcall +profile +visualextra
> +cryptv  +linebreak   +python  +viminfo
> +cscope  +lispindent  -python3 +vreplace
> +cursorbind  +listcmds+quickfix+wildignore
> +cursorshape +localmap+reltime +wildmenu
> +dialog_con_gui  +lua +rightleft   +windows
> +diff+menu+ruby+writebackup
> +digraphs+mksession   +scrollbind  +X11
> +dnd +modify_fname+signs   -xfontset
> -ebcdic  +mouse   +smartindent -xim
> +emacs_tags  +mouseshape  -sniff   -xsmp
> +eval+mouse_dec   +startuptime +xterm_clipboard
> +ex_extra-mouse_gpm   +statusline  -xterm_save
> +extra_search-mouse_jsbterm   -sun_workshop+xpm
>system vimrc file: "$VIM/vimrc"
>  user vimrc file: "$HOME/.vimrc"
>  2nd user vimrc file: "~/.vim/vimrc"
>   user exrc file: "$HOME/.exrc"
>   system gvimrc file: "$VIM/gvimrc"
> user gvimrc file: "$HOME/.gvimrc"
> 2nd user gvimrc file: "~/.vim/gvimrc"
> system menu file: "$VIMRUNTIME/menu.vim"
>   fall-back for $VIM: "
>
> /nix/store/n487qcmr3b2kvk1zis17s0d99z56pyfv-vim_configurable-7.4.335/share/vim
> "
> Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
> -I/nix/store/l03wlkdkn7hfyx1qgxm3q6h45q82and6-gtk+-2.24.24/include/gtk-2.0
>
> -I/nix/store/l03wlkdkn7hfyx1qgxm3q6h45q82and6-gtk+-2.24.24/lib/gtk-2.0/include
> -I/nix/store/5lg0s2rxgb5g2hhnld4aclhc2l7sx73y-glib-2.40.0/include/glib-2.0
>
> -I/nix/store/5lg0s2rxgb5g2hhnld4aclhc2l7sx73y-glib-2.40.0/lib/glib-2.0/include
> -I/nix/store/1a05vdqxkprlrmgyk0ny2h1p60afarkq-cairo-1.12.16/include/cairo
>
> -I/nix/store/s1n8g01x9slks39amxigr6l21gz2kp6n-freetype-2.5.3/include/freetype2
> -I/nix/store/s1n8g01x9slks39amxigr6l21gz2kp6n-freetype-2.5.3/include
>
> -I/nix/store/s1n8g01x9slks39amxigr6l21gz2kp6n-freetype-2.5.3/include/freetype2
> -I/nix/store/ir037n9vz50zinmwyx5531scmgi54mqs-fontconfig-2.10.2/include
>
> -I/nix/store/z9wmdhh6zaq0gd69ly4hrl0z245a4wpx-pango-1.32.5/include/pango-1.0
>
> -I/nix/store/s1iajj98g09lpnp1m2rdl3prss0hvyly-gdk-pixbuf-2.30.8/include/gdk-pixbuf-2.0
> -I/nix/store/w5lx36bqh4fk872mpy878sc2czab3h21-atk-2.12.0/include/atk-1.0
>-g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
> Linking: gcc -L/nix/store/l03wlkdkn7hfyx1qgxm3q6h45q82and6-gtk+-2.24.24/lib
> -L/nix/store/5lg0s2rxgb5g2hhnld4aclhc2l7sx73y-glib-2.40.0/lib
> -L/nix/store/1a05vdqxkprlrmgyk0ny2h1p60afarkq-cairo-1.12.16/lib
> -L/nix/store/s1n8g01x9slks39amxigr6l21gz2kp6n-freetype-2.5.3/lib
> -L/nix/store/ir037n9vz50zinmwyx5531scmgi54mqs-fontconfig-2.10.2/lib
> -L/nix/store/z9wmdhh6zaq0gd69ly4hrl0z245a4wpx-pango-1.32.5/lib
> -L/nix/store/s1iajj98g09lpnp1m2rdl3prss0hvyly-gdk-pixbuf-2.30.8/lib
> -L/nix/store/w5lx36bqh4fk872mpy878sc2czab3h21-atk-2.12.0/lib   -L.
> -rdynamic -Wl,-export-dynamic  -Wl,--as-needed -o vim
> -L/nix/store/l03wlkdkn7hfyx1qgxm3q6h45q82and6-gtk+-2.24.24/lib
> -L/nix/store/5lg0s2rxgb5g2hhnld4aclhc2l7sx73y-glib-2.40.0/lib
> -L/nix/store/1a05vdqxkprlrmgyk0ny2h1p60afarkq-cairo-1.12.16/lib
> -L/nix/store/s1n8g01x9slks39amxigr6l21gz2kp6n-freetype-2.5.3/lib
> -L/nix/store/ir037n9vz50zinmwyx5531scmgi54mqs-fontconfig-2.10.2/lib
> -L/nix/store/z9wmdhh6zaq0gd69ly4hrl0z245a4wpx-pango-1.32.5/lib
> -L/nix/store/s1iajj98g09lpnp1m2rdl3prss0hvyly-gdk-pixbuf-2.30.8/lib
> -L/nix/store/w5lx36bqh4fk872mpy878sc2czab3h21-atk-2.12.0/lib
> -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangoca

[Nix-dev] Fwd: Haskell doctest

2014-11-12 Thread Benno Fünfstück
Ah sorry, I wrote that on my phone so the answer was a bit short :).

You just type eval $buildPhase while you're in nix-shell. eval is a bash
builtin to execute a bash script from a string, and the buildPhase
environment variable contains the script that nix would use to build your
project when you'd use nix-build or similar. So eval $buildPhase just
builds your project but it also sets the GHC_PACKAGE_PATH environment
variable at the end, so that the tests can find the packages.

Since nix uses the `Setup.hs` file directly instead of going through
cabal-install, you will need to run eval $configurePhase once so that
Setup.hs gets compiled into the Setup executable and the project is
configured.

--
Benno

2014-11-12 18:52 GMT+01:00 Richard Wallace :

> Hi Benno,
>
> Thanks for the response.  I'm not sure what you mean by "eval $buildPhase"
> and where I would put that.  I'm stilling finding my feet with nix. :)
>
> Thanks again,
> Rich
>
> On Tue, Nov 11, 2014 at 11:01 PM, Benno Fünfstück <
> benno.fuenfstu...@gmail.com> wrote:
>
>> Hello Rich,
>>
>> GHC_PACKAGE_PATH needs to be set correctly for doctests to work. The
>> problem with this is that cabal doesn't work with GHC_PACKAGE_PATH set, so
>> you can't set it permanently.
>>
>> If you use "eval $buildPhase", that will build the project and set
>> GHC_PACKAGE_PATH.  doctests should work after that. You might need to run
>> eval "$configurePhase" before though, to compile Setup.hs.
>>
>> --
>> Benno
>>
>> Am 12.11.2014 00:51 schrieb "Richard Wallace" <
>> rwall...@thewallacepack.net>:
>>
>> >
>> > Hello all,
>> >
>> > We've got a Haskell project that we're using nix to ensure a consistent
>> build environment.  I'm working on adding tests with doctest, and am
>> running into trouble.  Here are the default.nix and shell.nix files we're
>> using (many dependencies elided for brevity)
>> >
>> > # This file was auto-generated by cabal2nix. Please do NOT edit
>> manually!
>> >
>> > { cabal, aeson, lens, doctest,
>> > }:
>> >
>> > cabal.mkDerivation (self: {
>> >   pname = "hiberico";
>> >   version = "1";
>> >   src = ./.;
>> >   isLibrary = false;
>> >   isExecutable = true;
>> >   buildDepends = [
>> > aeson lens
>> >   ];
>> >   testDepends = [
>> > doctest aeson lens
>> >   ];
>> >
>> >   meta = {
>> > description = "Iberico in Haskell";
>> > license = "unknown";
>> > platforms = self.ghc.meta.platforms;
>> >   };
>> > })
>> >
>> > # shell.nix
>> > let
>> >nixpkgs = (import  {}).fetchgit {
>> > url = "git://github.com/NixOS/nixpkgs.git";
>> > rev = "c758ec756b60a2161a5d7369d07d3eb2fe04a5aa";
>> > sha256 = "01x01gwj2pm165sdhb1fxfdzl638kksx79dyadji5f2wp4hssk8m";
>> >   };
>> > in
>> >   { system ? builtins.currentSystem
>> >   , pkgs ? import nixpkgs { inherit system; }
>> >   , haskellPackages ? pkgs.haskellPackages.override {
>> >   extension = self: super: {
>> > hiberico = self.callPackage ./. {};
>> >   };
>> > }
>> >   }:
>> >   pkgs.lib.overrideDerivation haskellPackages.hiberico (attrs: {
>> > buildInputs = [
>> >   haskellPackages.cabalInstall
>> > ] ++ attrs.buildInputs;
>> >   })
>> >
>> >
>> > When I enter the nix-shell (`nix-shell --pure shell.nix`), the
>> environment seems setup correctly.  I can run `cabal configure
>> --enable-tests && cabal build && cabal test` and it gets to the point where
>> doctest is parsing the source files and I get
>> >
>> > Building hiberico-1...
>> > Preprocessing executable 'hiberico' for hiberico-1...
>> > Preprocessing test suite 'doctests' for hiberico-1...
>> > Running 1 test suites...
>> > Test suite doctests: RUNNING...
>> >
>> > src/Topology.hs:11:18:
>> > Could not find module 'Data.Aeson'
>> > Perhaps you meant Data.Version (from base)
>> > Use -v to see a list of the files searched for.
>> >
>> > I've added all the dependencies to the doctests suite in the cabal
>> file. Is there something else I'm missing?
>> >
>> > Thanks,
>> > Rich
>> >
>> > ___
>> > 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] clang-based stdenv for OSX Yosemite

2014-11-12 Thread Eric Seidel
Can you update to the latest joelteon/master (3b57c2b) and build Python again? 
Joel's hydra seems to be building Python just fine at the moment, and I've also 
just done it locally without issue.

Thanks!
Eric


> On Nov 12, 2014, at 07:20, Wout Mertens  wrote:
> 
> So on a fresh 10.10 with XCode 6.1 the joelteon master branch can't build 
> things like Python. The error is below, I presume it is because the 
> downloaded clang depends on libraries that aren't available. Should I just 
> rebuild the world without binary cache?
> 
> configure:3947: checking whether the C compiler works
> 
> configure:3969: clang  
> -I/nix/store/0vxclyfimw81d5a42z5awxmkvl3zgl1x-zlib-1.2.8/include 
> -I/nix/store/0x4dqky1g3jvwvadcw51najjj0a6ibiq-bzip2-1.0.6/include 
> -I/nix/store/0zma7049nw3mwq8aik183i2mbpgw2426-xz-5.0.5/include 
> -I/nix/store/i49hpms5d8j0cg2izjxnzyl9b02s508j-gdbm-1.11/include 
> -I/nix/store/z1sh0nlnwlv0yma6c91m55fq9zr9d9fa-sqlite-3.8.7/include 
> -I/nix/store/igmjzlrkczlzggaplyi3makxfm9iqvkg-db-5.3.28/include 
> -I/nix/store/m8gw7ggzdny8p2w9dik9f481pmjwmpma-readline-6.3p08/include 
> -I/nix/store/fc688jhpqkbjxhn8xnksswpv5szcvdxg-ncurses-5.9/include 
> -I/nix/store/89zxnpdrhv2z9lffhhmjac52dspqqpi4-openssl-1.0.1j/include 
> -I/nix/store/rah8sp90y0aml9495av4w6ls3y7vjdnj-tcl-8.5.15/include 
> -I/nix/store/7yhp7w16wnq206x4qih2fzfkkbm7s558-tk-8.5.15/include 
> -I/nix/store/kpfyi3q82iblsnb663ybksnas5g09x3q-libX11-1.6.2/include 
> -I/nix/store/wxv9vgqi60dhxm33q10lh0wx8p8l1glk-xproto-7.0.26/include 
> -L/nix/store/0vxclyfimw81d5a42z5awxmkvl3zgl1x-zlib-1.2.8/lib 
> -L/nix/store/0x4dqky1g3jvwvadcw51najjj0a6ibiq-
 bzip2-1.0.6/lib -L/nix/store/0zma7049nw3mwq8aik183i2mbpgw2426-xz-5.0.5/lib 
-L/nix/store/i49hpms5d8j0cg2izjxnzyl9b02s508j-gdbm-1.11/lib 
-L/nix/store/z1sh0nlnwlv0yma6c91m55fq9zr9d9fa-sqlite-3.8.7/lib 
-L/nix/store/igmjzlrkczlzggaplyi3makxfm9iqvkg-db-5.3.28/lib 
-L/nix/store/m8gw7ggzdny8p2w9dik9f481pmjwmpma-readline-6.3p08/lib 
-L/nix/store/fc688jhpqkbjxhn8xnksswpv5szcvdxg-ncurses-5.9/lib 
-L/nix/store/89zxnpdrhv2z9lffhhmjac52dspqqpi4-openssl-1.0.1j/lib 
-L/nix/store/rah8sp90y0aml9495av4w6ls3y7vjdnj-tcl-8.5.15/lib 
-L/nix/store/7yhp7w16wnq206x4qih2fzfkkbm7s558-tk-8.5.15/lib 
-L/nix/store/kpfyi3q82iblsnb663ybksnas5g09x3q-libX11-1.6.2/lib 
-L/nix/store/wxv9vgqi60dhxm33q10lh0wx8p8l1glk-xproto-7.0.26/lib conftest.c  
-lncurses >&5
> 
> ld: library not found for -lcrt1.10.6.o
> 
> clang-3.5: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> 
> 
> On Fri Nov 07 2014 at 6:23:57 PM Eric Seidel  wrote:
> Alfredo Di Napoli  writes:
> 
> > Thank you so much guys for your stoic effort!
> > For the nix newbies like me, could you please expand upon
> > "If you would like to use our branch you should add hydra.joelt.io to your
> > binary caches."
> 
> You want to set the binary-caches option in nix.conf, e.g.
> 
>   binary-caches = http://cache.nixos.org http://hydra.joelt.io
> 
> I think nix looks for /etc/nix/nix.conf by default, but this is
> configurable via the NIX_CONF_DIR environment variable.
> 
> Eric
> ___
> 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