Hi Andres,
> I tried and I can't reproduce this. Is this a problem on your
> machine, or on Hydra? And how many cores are you using?
I had that problem on my machine, building in a chroot environment
with 12 cores. I've had the same error with earlier versions of GHC,
too, but usually the probl
Hi Peter.
> I got the following error in 4 consecutive attempts:
>
> building rts/dist/build/AutoApply.debug_o
> building rts/dist/build/AutoApply.thr_o
> rts_dist_HC rts/dist/build/AutoApply.debug_o
> /nix/store/1iigiim5855m8j7pmwf5xrnpf705s4dh-binutils-2.21.1a/bin/ld: cannot
> find
>
Excerpts from Marc Weber's message of Thu Sep 13 16:14:20 +0200 2012:
> Would you mind listening the advantages causing you to propose the
sorry - I meant "listing". Should have been clear from context though.
Marc Weber
___
nix-dev mailing list
nix-dev@
Hi Eelco,
Would you mind listening the advantages causing you to propose the
switch one day?
If there are strong reasons I'll try to help fix remaining bugs.
Marc Weber
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mai
Den 2012-09-13 09:01:43 skrev Mathijs Kwik :
> Eelco Dolstra writes:
>
>> Hi,
>>
>> On 12/09/12 11:12, Mathijs Kwik wrote:
>>
>>> Currently (with upstart), network interfaces tigger ip-up once dhcpcd
>>> assigns them an ip-address.
>>> Upstart triggers had an option to supply extra params, and dh
Eelco Dolstra writes:
> Hi,
>
> On 12/09/12 11:12, Mathijs Kwik wrote:
>
>> Currently (with upstart), network interfaces tigger ip-up once dhcpcd
>> assigns them an ip-address.
>> Upstart triggers had an option to supply extra params, and dhcpcd's
>> hook used this to supply information on which
