Fis Trivial writes:
> Ludovic Courtès writes:
>
>> Hi,
>>
>> Fis Trivial skribis:
>>
> However, I wanted to manage all of these with guix so that we can have a
> unified dependency tree. Currently there are a few options for OpenCL
> runtime. Namely, beignet, neo from Intel, ROCm sta
Ludovic Courtès writes:
> Hi,
>
> Fis Trivial skribis:
>
However, I wanted to manage all of these with guix so that we can have a
unified dependency tree. Currently there are a few options for OpenCL
runtime. Namely, beignet, neo from Intel, ROCm stack from AMD, the POCL
proj
On a commit from ~30 minutes ago, guix pull fails:
substitute: updating list of substitutes from 'https://berlin.guixsd.org'...
100.0%
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'...
100.0%
The following derivations will be built:
/gnu/store/7b8zpi91v86hna3sch8lpx
l...@gnu.org (Ludovic Courtès) writes:
> Chris Marusich skribis:
>
>> On February 22nd, Nix 2.0 was released:
>>
>> https://nixos.org/nix/manual/#ssec-relnotes-2.0
>
> Very nice work. It looks like the CLI is closer to that of Guix now. :-)
>
>> It contains a lot of interesting new features. A
Chris Marusich transcribed 1.4K bytes:
> Hi,
>
> On February 22nd, Nix 2.0 was released:
>
> https://nixos.org/nix/manual/#ssec-relnotes-2.0
>
> It contains a lot of interesting new features. Are there any plans to
> merge some of the nix-daemon changes into our guix-daemon? Is
> compatibility
Hello!
Chris Marusich skribis:
> On February 22nd, Nix 2.0 was released:
>
> https://nixos.org/nix/manual/#ssec-relnotes-2.0
Very nice work. It looks like the CLI is closer to that of Guix now. :-)
> It contains a lot of interesting new features. Are there any plans to
> merge some of the n
Welcome Sandeep, and thank you reepca for offering to help!
Ludo’.
My previous message is still in the whitelisting time, but:
First I ran guix pull (3rd guix pull with new guix pull mechanism). An error
occured.
I ran it again, error gone.
The following derivations will be built:
/gnu/store/7b8zpi91v86hna3sch8lpx45qzngnb38-guix-df1eaffc3.drv
/gnu/store/l4zws3m
Hartmut Goebel writes:
> Am 28.04.2018 um 12:11 schrieb Chris Marusich:
>
>> Because the python-build-system never cross-compiles,
>
> This is an implementation detail which might might change. And if we
> remove all inputs now, we need to add again them later. This is a lot of
> work, I know si
Hi,
Jose Garza skribis:
> What kind of effort do you think this would take? Is this a good first
> commit?
It requires familiarity with Scheme and Haunt, I suppose.
swedebugia skribis:
> The source code is not available via the git repository on that page and
> neither anywhere else accordi
Hi,
Fis Trivial skribis:
>>> However, I wanted to manage all of these with guix so that we can have a
>>> unified dependency tree. Currently there are a few options for OpenCL
>>> runtime. Namely, beignet, neo from Intel, ROCm stack from AMD, the POCL
>>> project and the implementation in mesa.
Fis Trivial writes:
> I'm confused, some native-inputs are for testing. They shouldn't be
> installed in normal case.
native-inputs are not only for testing. More generally, when
cross-compiling, any programs that must be run on the build machine must
be 'native-inputs'. Any programs that must
12 matches
Mail list logo
