From: Arthur Cohen <arthur.cohen@embecosm.com>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
gcc-rust@gcc.gnu.org
Subject: Re: [PATCH] build: Check for cargo when building rust language
Date: Tue, 9 Apr 2024 14:01:02 +0200 [thread overview]
Message-ID: <4840931e-1b05-4a95-a06f-662667e34d42@embecosm.com> (raw)
In-Reply-To: <DFF24C6D-24EF-4C7F-9334-051250CC352E@googlemail.com>
Hi Iain!
On 4/9/24 10:55, Iain Sandoe wrote:
> Hi Arthur,
>
>> On 9 Apr 2024, at 11:40, Arthur Cohen <arthur.cohen@embecosm.com> wrote:
>
>> On 4/9/24 09:47, John Paul Adrian Glaubitz wrote:
>>> Hello,
>>> On Mon, 2024-04-08 at 18:33 +0200, pierre-emmanuel.patry@embecosm.com wrote:
>>>> The rust frontend requires cargo to build some of it's components,
>>>> it's presence was not checked during configuration.
>>> Isn't this creating a hen-and-egg problem? How am I supposed to build a Rust
>>> compiler for a target which is not supported by rustc (yet) when gccrs is
>>> supposed to build-depend on cargo which requires rustc?
>>> Adrian
>>
>> Quick reminder in case you haven't seen our Request for Comments on the main ML that this is only a temporary solution. Once gccrs can compile its dependencies, we'll go through a more "classical" bootstrapping chain.
>
>
> I don’t suppose there’s some way to make a “download prerequisites” action for this?
Do you mean downloading cargo/Rust as a prerequisite? I don't believe
this is being done for GNAT/GDC, but I might be wrong.
If you mean the dependencies for our Rust components, those are
currently being vendored so that we're able to build them offline. I'll
push the commits soon.
>
> (I realise that the prerequisite might not be available for a given platform - but then the configure will then just fail to detect them and carry on).
>
> At the least the build documentation requested should (ideally) try to lower the barrier to finding the deps and give reliable sources for them.
>
>> rustc_codegen_gcc can probably already be used for building these dependencies however, if you'd like to have a look at that.
>
> Detailing the verious options would also be a helpful part of the build doc.
>
> thanks
> Iain
>
Best,
Arthur
next prev parent reply other threads:[~2024-04-09 10:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 16:33 pierre-emmanuel.patry
2024-04-09 7:42 ` Richard Biener
2024-04-09 7:47 ` John Paul Adrian Glaubitz
2024-04-09 8:00 ` Jakub Jelinek
2024-04-09 8:29 ` John Paul Adrian Glaubitz
2024-04-09 10:40 ` Arthur Cohen
2024-04-09 8:55 ` Iain Sandoe
2024-04-09 12:01 ` Arthur Cohen [this message]
2024-04-09 10:09 ` Iain Sandoe
2024-04-09 13:53 ` Arthur Cohen
2024-04-09 14:12 ` Andrew Pinski
2024-04-09 14:25 ` Arthur Cohen
2024-04-15 11:14 ` Thomas Schwinge
2024-04-15 11:50 ` build: Don't check for host-prefixed 'cargo' program (was: [PATCH] build: Check for cargo when building rust language) Thomas Schwinge
2024-04-15 12:18 ` build: Don't check for host-prefixed 'cargo' program Pierre-Emmanuel Patry
2024-04-15 12:44 ` build: Use of cargo not yet supported here in Canadian cross configurations (was: [PATCH] build: Check for cargo when building rust language) Thomas Schwinge
2024-04-15 16:36 ` build: Use of cargo not yet supported here in Canadian cross configurations Pierre-Emmanuel Patry
2024-04-16 8:55 ` Arthur Cohen
2024-04-16 20:34 ` [PATCH] build: Check for cargo when building rust language Andrew Pinski
2024-04-17 8:13 ` Rainer Orth
2024-04-17 14:54 ` Arthur Cohen
2024-04-23 8:52 ` Rainer Orth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4840931e-1b05-4a95-a06f-662667e34d42@embecosm.com \
--to=arthur.cohen@embecosm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=idsandoe@googlemail.com \
--cc=pierre-emmanuel.patry@embecosm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).