Hi,
Maxim Cournoyer skribis:
>> Ludovic Courtès writes:
[...]
>>> Perhaps we can address all this in several steps:
>>>
>>> 1. apply the librsvg 2.40 hack now so we can merge
>>> ‘core-updates-frozen’ this week for real;
[...]
> I hear your frustration w.r.t to delays; I don't mind i
Hi Maxim,
Maxim Cournoyer skribis:
> I've refreshed the branch again, and now there are no performance
> problems with the cross-built rustc.
>
> But Ludovic mentioned that the binary would need to be statically linked
> rather than dynamically linked, and in the case of rustc that
> complicates
Hello again,
I've refreshed the branch again, and now there are no performance
problems with the cross-built rustc.
But Ludovic mentioned that the binary would need to be statically linked
rather than dynamically linked, and in the case of rustc that
complicates things because it relies on dynami
Hi again, Ludovic et al!
I'm trying another direction in my reply here based on recent findings;
Ludovic Courtès writes:
> Hi!
>
> Maxim Cournoyer skribis:
>
>> I've updated the branch wip-cross-built-rust; it seems to build and run
>> OK (although running the binary produced by compiling hell
Hi Ludovic,
Ludovic Courtès writes:
> Hi!
>
> Maxim Cournoyer skribis:
>
>> I've updated the branch wip-cross-built-rust; it seems to build and run
>> OK (although running the binary produced by compiling hello.rs with the
>> cross-built i686-linux rustc in a 32 bit VM took 47 sec (!?)),
>> app
Hi!
Maxim Cournoyer skribis:
> I've updated the branch wip-cross-built-rust; it seems to build and run
> OK (although running the binary produced by compiling hello.rs with the
> cross-built i686-linux rustc in a 32 bit VM took 47 sec (!?)),
> apparently hanging on something before outputting co
Hello!
I've updated the branch wip-cross-built-rust; it seems to build and run
OK (although running the binary produced by compiling hello.rs with the
cross-built i686-linux rustc in a 32 bit VM took 47 sec (!?)),
apparently hanging on something before outputting correctly the message
and exiting
Hello,
Ricardo Wurmus writes:
> Ludovic Courtès writes:
>
>> We could try that, but IMO we first need a solution within days—we
>> just
>> cannot reasonably let this branch go on for longer than that. The
>> librsvg 2.40 hack would give us Xfce (maybe GNOME?) on i686 today.
>>
>> Perhaps we can
Ludovic Courtès writes:
We could try that, but IMO we first need a solution within
days—we just
cannot reasonably let this branch go on for longer than that.
The
librsvg 2.40 hack would give us Xfce (maybe GNOME?) on i686
today.
Perhaps we can address all this in several steps:
1. appl
Hi,
Maxim Cournoyer skribis:
> I'd like to revise my position, as I got confirmation that it ought to
> be possible to cross-build rustc for other architectures from our
> (cleanly bootstrapped) x86_64 rustc!
[...]
> I haven't yet done any reading, but if Mutabah (the author of mrustc)
> says
Tobias Platen writes:
On Sat, 2021-11-27 at 19:43 -0800, John Soo wrote:
Hi Guix,
I had the same thought as Maxim. In my quest for arm support
for ghc,
I thought about using a cross-compiled version. Is this
possible or
even desirable? I think for rust and ghc it would be very
helpful -
On Sat, 2021-11-27 at 19:43 -0800, John Soo wrote:
> Hi Guix,
>
> I had the same thought as Maxim. In my quest for arm support for ghc,
> I thought about using a cross-compiled version. Is this possible or
> even desirable? I think for rust and ghc it would be very helpful -
> if somewhat less pr
Hi Guix,
I had the same thought as Maxim. In my quest for arm support for ghc, I thought
about using a cross-compiled version. Is this possible or even desirable? I
think for rust and ghc it would be very helpful - if somewhat less principled
than a bootstrap all the way up (on the same compute
Hello again,
Maxim Cournoyer writes:
[...]
>> There is also the unpleasant option to introduce a rust binary for
>> architectures other than x86_64, because we can’t bootstrap it
>> there. It should be noted that this would not be unprecedented. We
>> have bootstrap binaries for some compiler
Hello,
Ricardo Wurmus writes:
> Ludovic Courtès writes:
>
>> As you may know, librsvg 2.50 on ‘core-updates-frozen’ depends on
>> Rust.
>> However mrustc, which we use to build the first Rust compiler,
>> currently
>> only works on x86_64. This means that ~28% of the packages on
>> ‘core-updat
Ludovic Courtès writes:
As you may know, librsvg 2.50 on ‘core-updates-frozen’ depends
on Rust.
However mrustc, which we use to build the first Rust compiler,
currently
only works on x86_64. This means that ~28% of the packages on
‘core-updates-frozen’ are x86_64-only (vs. ~15% on ‘master’
Hello Guix!
As you may know, librsvg 2.50 on ‘core-updates-frozen’ depends on Rust.
However mrustc, which we use to build the first Rust compiler, currently
only works on x86_64. This means that ~28% of the packages on
‘core-updates-frozen’ are x86_64-only (vs. ~15% on ‘master’).
Among these, th
17 matches
Mail list logo
