> Michael Sperber writes:
> Also, maybe I misunderstood you - what do you mean by "reference"? It seems
> the reference is in gcc itself - the C file I'm compiling is trivial:
> [nix-shell:~/]$ gcc ~/temp/x.c
> ld: file not found: /usr/lib/system/libsystem_coreservices.dylib for
> architec
Thanks for the prompt reply!
"John Wiegley" writes:
>> Michael Sperber writes:
>
>> \[\][nix-shell:~/temp]$\[\] gcc x.c
>> ld: file not found: /usr/lib/system/libsystem_coreservices.dylib for
>> architecture x86_64
>> collect2: error: ld returned 1 exit status
>
>> I'm stumped with this.
> Michael Sperber writes:
> \[\][nix-shell:~/temp]$\[\] gcc x.c
> ld: file not found: /usr/lib/system/libsystem_coreservices.dylib for
> architecture x86_64
> collect2: error: ld returned 1 exit status
> I'm stumped with this. Just to be sure, I built gccApple from source, but
> the proble
I'm +1 on this one. Hydra evaluates nixpkgs very fast.
I'm only worried if the email is per build, not per jobset evaluation. Is
that the case?
PS: Ideally it would test every commit (or bisect failing commit).
On Thu, Oct 23, 2014 at 8:25 PM, Vladimír Čunát wrote:
> Cheers!
>
> On 10/23/2014
Cheers!
On 10/23/2014 06:57 PM, Domen Kožar wrote:
Now it's *only* about keeping it that way ;-)
Well, what about Hydra notifying committers/authors of changes that
(probably) cause build breakages? IIRC it's just about enabling a
switch, and in the current state it might not generate so muc
On 23 October 2014 18:57, Domen Kožar wrote:
> We're pretty much done getting failures to zero:
> http://hydra.nixos.org/jobset/nixos/trunk-combined
Awesome! Thanks to everyone helping out. (I feel ashamed for not doing
so myself.)
I remember first time I looked at Hydra, maybe 2 years ago. I wa
Wow! Amazing!! :) Thanks for all the effort! Thomas
On 10/23/2014 06:57 PM, Domen Kožar wrote:
> We're pretty much done getting failures to zero:
> http://hydra.nixos.org/jobset/nixos/trunk-combined
>
> Now it's *only* about keeping it that way ;-)
>
> On Thu, Oct 9, 2014 at 5:28 PM, Domen Kožar
We're pretty much done getting failures to zero:
http://hydra.nixos.org/jobset/nixos/trunk-combined
Now it's *only* about keeping it that way ;-)
On Thu, Oct 9, 2014 at 5:28 PM, Domen Kožar wrote:
> Last two packages and a test:
>
> - linuxPackages_latest.netatop http://hydra.nixos.org/build/15
Hi all,
I have volunteered to be release manager of Caterpillar. I'd like to fix
two dates for the release:
- 20.11: I'll branch off master into `release-14.11`, from that point on
we'll be testing and applying bugfixes
- 30.11: final release of NixOS 14.11
Documentation about release process, p
Hi,
On Wed, Oct 22, 2014 at 5:35 PM, Luca Bruno wrote:
> I appreciate the work being done by Domen and jumping in as release
> manager.
>
thanks!
> I'd like to point out a few things however about the milestone issues. The
> release should be due for October 31th, and in my vision the date i
Nix used to work fine for me on Mac OS X, but today it acted up by way
of gcc stopping to work:
> nix-shell ~/build/nixpkgs -A cyrus_sasl
\[\][nix-shell:~/temp]$\[\] gcc x.c
ld: file not found: /usr/lib/system/libsystem_coreservices.dylib for
architecture x86_64
collect2: error: ld returned 1 e
>If this thing would be supported, this would give us a good reason to
>push our nix expressions upstream. This would have at least 2 good
>impacts:
>
>- a growing awareness of nix
>- a nice way for all developers to build their package
- Ease of integration of Nix-related tools thatt already come
Hi,
imagine an upstream tarball includes a nix expression to build and
install the tarball. How can I reuse this nix expression when I
propose the package to NixOS/nixpkgs? By "reuse", I *do not* include
copy/pasting.
If this thing would be supported, this would give us a good reason to
push our
On 23 October 2014 15:46, Pierre Allix wrote:
> Hi,
>
> When executing bash directly from the store, I get the following errors:
>
> Any ideas?
>
> ./nix/env/bin/bash
> bash: lesspipe: command not found
> bash: shopt: progcomp: invalid shell option name
> bash: complete: command not found
[...]
W
Hi,
When executing bash directly from the store, I get the following errors:
Any ideas?
./nix/env/bin/bash
bash: lesspipe: command not found
bash: shopt: progcomp: invalid shell option name
bash: complete: command not found
bash: complete: command not found
bash: complete: command not found
bash
Hi!
On 10/22/2014 05:42 PM, Eelco Dolstra wrote:
That's November 30th (we changed it to 14.11).
Maybe we should call it 14.12 and release at the start of December :-)
We'll see how it goes. IMO solving the issues is more important than the
scheduled date. I think we also want staging stuff i
16 matches
Mail list logo
