public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
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 15:53:24 +0200	[thread overview]
Message-ID: <2746644b-54d7-43ac-932b-dfc49d7bbaed@embecosm.com> (raw)
In-Reply-To: <10C938E8-1018-405B-8044-77C1C4444FFE@googlemail.com>



On 4/9/24 12:09, Iain Sandoe wrote:
> Hi Arthur,
> 
>> On 9 Apr 2024, at 13:01, Arthur Cohen <arthur.cohen@embecosm.com> wrote:
>>
> 
>> 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.
> 
> No, you are quite correct, but the critical difference is that Ada and D both make use of earlier versions of GCC - so that (if one wished to be particular) it is possible to start with an earlier version of GCC and work forwards (in fact that’s what I’ve [I guess all of us] have done for D … and did a looong time ago for Ada).
> 
> The difference here is that we need to install an executable from somewhere else - and making that as simple and trustworthy as possible seems like a good move to encourage folks to build & test rust.

Ah, that's fair. I guess it will require some modifications to the 
script though, as I would not want to impose Rust on anyone not looking 
to compile gccrs. I'll add this to the list of things to work on before 
14.1 :)

Thanks!

> 
>> 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.
> 
> OK.. I’m sorry to say this - but what’s actually needed is still a little fuzzy to me - but I am happy to wait to read the documentation patch and comment then.
> 
> thanks
> Iain
> 
>>
>>> (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
> 

  reply	other threads:[~2024-04-09 13:53 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
2024-04-09 10:09         ` Iain Sandoe
2024-04-09 13:53           ` Arthur Cohen [this message]
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=2746644b-54d7-43ac-932b-dfc49d7bbaed@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).