Hello all,
I'm trying to get this working.
[stewart@rivergod:~/dev/fractalide/dmichiels/fractalide]$
./result/bin/development_test
thread '' panicked at 'called `Result::unwrap()` on an `Err`
value: "SDL error: Failed loading libGL.so.1: dlopen: cannot load any
more object with static TLS"', src/
Hello Nixers*:
I want to be able to do the following steps:
## On the build server
1. build nix closures in a non-hydra build system
2. export the closure, somehow contained into a single file
3. upload this file to an artifact store
## On another server
1. download the file from the artifact st
You shouldn't but In the mean time use `xcode-select --install` to just
install the command-line tools. It should save you some space.
On Wed, 24 Feb 2016 at 14:01 Anders Lundstedt
wrote:
> I use Nix on OS X 10.11.3. "nix-env -iA nixpkgs.vimHugeX" fails
> because the otool command is not availa
I use Nix on OS X 10.11.3. "nix-env -iA nixpkgs.vimHugeX" fails
because the otool command is not available. I am prompted by the OS to
"install Xcode and the command line developer tools from the App
Store".
Github issue:
https://github.com/NixOS/nixpkgs/issues/12670
_
Unfortunately, the Torch build from
https://github.com/grwlf/torch-distro has a Segfault problem.
$ th
th> N = 5
[0.s]
th> A = torch.rand(N, N)
[0.0002s]
What I take from this thread is not that we need to enforce ownership (I
think it is right to say that the people committing to nixpkgs are cautious
to only commit to their own stuff), but rather that we need to document
this ownership better. Just a file, like chromiums OWNERS files could help
ver
Dear All,
I am following this
https://bluishcoder.co.nz/2014/05/14/installing-nixos-with-encrypted-root-on-thinkpad-w540.html
and this http://chris-martin.org/2015/installing-nixos/ guide to install LVM
and LUKS on my 1 SSD and 1 HDD. Below are my detail configuration:
1. SSD:
/dev/sda1 1M
> I'm totally for that, but do note that there is an equivalent problem
> in deciding who gets "PR approval" access. But, I suppose since we
> control hydra/whatever and not github, we can roll our own logic like
> allowing people to only approve PRs for automatic merging that affect
> certain file
>
>I started writing some docbook. Maybe I will get used to it but writing
>`foobar` is way more
>painful that `* foobar` in markdown. Especially in writing I think it's
>important to be able to move text around without too much overhead so that
>text can be reworked until it feels right.
I also r
