From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v10 01/10] rustc: new virtual package
Date: Fri, 9 Feb 2018 09:56:10 +0100 [thread overview]
Message-ID: <20180209095610.5f4fa6a5@windsurf.lan> (raw)
In-Reply-To: <20180209084906.GB6503@itchy>
Hello,
On Fri, 9 Feb 2018 09:49:06 +0100, Eric Le Bihan wrote:
> > check-package is not happy with RUST_TARGET_NAME and RUST_HOST_NAME
> > because they don't have a RUSTC_ prefix, even though they are defined
> > in rustc.mk:
> >
> > ./package/rustc/rustc.mk:10: possible typo: RUST_TARGET_NAME -> *RUSTC*
> > ./package/rustc/rustc.mk:18: possible typo: RUST_HOST_NAME -> *RUSTC*
> >
> > Would renaming them to RUSTC_TARGET_NAME and RUSTC_HOST_NAME make
> > sense ? Or do we need to keep RUST_TARGET_NAME/RUST_HOST_NAME and add
> > an exception in check-package ?
>
> I do not see any problems using RUSTC_{HOST,TARGET}_NAME: it still caries
> the same information as RUST_{HOST,TARGET}_NAME.
Question is: are these host and target names "Rust" related, or "Rust
compiler" related. If they are Rust related, the current RUST_ prefix
makes more sense. If they are specific to the Rust compiler, then
RUSTC_ would make more sense. If it isn't clear, then we can use RUSTC_
to avoid the problem :-)
If you are happy with RUSTC_, could you submit a patch against "master"
that does the renaming ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-09 8:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 18:07 [Buildroot] [PATCH v10 00/10] Add support for the Rust programming language Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 01/10] rustc: new virtual package Eric Le Bihan
2018-02-08 22:52 ` Thomas Petazzoni
2018-02-09 8:49 ` Eric Le Bihan
2018-02-09 8:56 ` Thomas Petazzoni [this message]
2018-02-09 18:11 ` Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 02/10] rust-bin: new package Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 03/10] cargo-bin: " Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 04/10] rust: " Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 05/10] libssh2: add host variant Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 06/10] libhttpparser: " Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 07/10] libcurl: " Eric Le Bihan
2018-02-04 18:07 ` [Buildroot] [PATCH v10 08/10] cargo: new package Eric Le Bihan
2018-02-05 10:26 ` Peter Korsgaard
2018-02-05 13:11 ` Sam Voss
2018-02-05 13:58 ` Peter Korsgaard
2018-02-04 18:07 ` [Buildroot] [PATCH v10 09/10] docs/manual: document cargo-based packages Eric Le Bihan
2018-02-05 10:29 ` Peter Korsgaard
2018-02-04 18:07 ` [Buildroot] [PATCH v10 10/10] support/testing: add tests for Rust Eric Le Bihan
2018-02-05 14:03 ` [Buildroot] [PATCH v10 00/10] Add support for the Rust programming language Peter Korsgaard
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=20180209095610.5f4fa6a5@windsurf.lan \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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