David Craven skribis:
>> Would that help?
>
> Awesome! Thank you.
>
> The bootstrapping solution turned out much better. I added the
> #:system argument to rustc-bootstrap and cargo-bootstrap and moved the
> gcc -> cc symlink into rust-bootstrap, so that we get a native
> toolchain. We can build
> Would that help?
Awesome! Thank you.
The bootstrapping solution turned out much better. I added the
#:system argument to rustc-bootstrap and cargo-bootstrap and moved the
gcc -> cc symlink into rust-bootstrap, so that we get a native
toolchain. We can build rustc on i686 and x86_64 using the sa
David Craven skribis:
>> Hmm why is there a second one? ‘gnu-build-system’ already provides gcc
>> and gcc:lib as implicit inputs, so maybe it’s just a matter of removing
>> ‘gcc’ from Rust’s ‘inputs’?
>
> So we do have an implicit gcc:lib package as an input. But I have to patchelf
> the rustc
> Hmm why is there a second one? ‘gnu-build-system’ already provides gcc
> and gcc:lib as implicit inputs, so maybe it’s just a matter of removing
> ‘gcc’ from Rust’s ‘inputs’?
So we do have an implicit gcc:lib package as an input. But I have to patchelf
the rustc binaries and libraries so I need
Hi David!
David Craven skribis:
>> Given the work that has gone into these Rust patches, I think it would
>> be nice to apply them and possibly document any shortcoming or future
>> work items.
>
> I went over all your previous emails and fixed your previous comments.
> Those aren't part of the
Hi Ludo!
> Given the work that has gone into these Rust patches, I think it would
> be nice to apply them and possibly document any shortcoming or future
> work items.
I went over all your previous emails and fixed your previous comments.
Those aren't part of the new patch series yet...
In summa
ng0 skribis:
> Ludovic Courtès writes:
>
>> David Craven skribis:
>>
>>> * guix/build-system/cargo.scm (default-cargo, default-rustc,
>>> %cargo-build-system-modules, cargo-build, lower, cargo-build-system):
>>> New variables.
>>> * guix/build/cargo-build-system.scm (configure, build, check
Ludovic Courtès writes:
> David Craven skribis:
>
>> * guix/build-system/cargo.scm (default-cargo, default-rustc,
>> %cargo-build-system-modules, cargo-build, lower, cargo-build-system):
>> New variables.
>> * guix/build/cargo-build-system.scm (configure, build, check, install,
>> %standar
David Craven skribis:
> * guix/build-system/cargo.scm (default-cargo, default-rustc,
> %cargo-build-system-modules, cargo-build, lower, cargo-build-system):
> New variables.
> * guix/build/cargo-build-system.scm (configure, build, check, install,
> %standard-phases, cargo-build): New variab
> Is this correct? What happens when test-target is not specified? I see
> below that the target is hard-coded to “test”. Maybe set it to “test”
> here and use it on the build side?
> Shouldn’t this respect “test-target”?
There is no other build target than test. Functions that are tests
have
David Craven writes:
> * guix/build-system/cargo.scm (default-cargo, default-rustc,
> %cargo-build-system-modules, cargo-build, lower, cargo-build-system):
> New variables.
> * guix/build/cargo-build-system.scm (configure, build, check, install,
> %standard-phases, cargo-build): New variab
* guix/build-system/cargo.scm (default-cargo, default-rustc,
%cargo-build-system-modules, cargo-build, lower, cargo-build-system):
New variables.
* guix/build/cargo-build-system.scm (configure, build, check, install,
%standard-phases, cargo-build): New variables.
---
guix/build-system/cargo.
12 matches
Mail list logo
