public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@baylibre.com>
To: Christophe Lyon <christophe.lyon@linaro.org>, gcc-patches@gcc.gnu.org
Cc: gcc-rust@gcc.gnu.org, arthur.cohen@embecosm.com,
	herron.philip@googlemail.com
Subject: Re: [PATCH] rust: Add rust.install-dvi and rust.install-html rules
Date: Mon, 08 Apr 2024 23:26:49 +0200	[thread overview]
Message-ID: <87edbf4kbq.fsf@euler.schwinge.ddns.net> (raw)
In-Reply-To: <20240404162719.3737066-1-christophe.lyon@linaro.org>

Hi Christophe!

On 2024-04-04T16:27:19+0000, Christophe Lyon <christophe.lyon@linaro.org> wrote:
> rust has the (empty) rust.dvi and rust.html rules, but lacks the
> (empty) rust.install-dvi and rust.install-html ones.

Thanks, looks good to me.


Grüße
 Thomas


> 2024-04-04  Christophe Lyon  <christophe.lyon@linaro.org>
>
> 	gcc/rust/
> 	* Make-lang.in (rust.install-dvi, rust.install-html): New rules.
> ---
>  gcc/rust/Make-lang.in | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/gcc/rust/Make-lang.in b/gcc/rust/Make-lang.in
> index 4d646018792..4d73412739d 100644
> --- a/gcc/rust/Make-lang.in
> +++ b/gcc/rust/Make-lang.in
> @@ -342,6 +342,8 @@ selftest-rust-valgrind: $(RUST_SELFTEST_DEPS)
>  # should have dependencies on info files that should be installed.
>  rust.install-info:
>  
> +rust.install-dvi:
> +rust.install-html:
>  rust.install-pdf:
>  
>  # Install man pages for the front end. This target should ignore errors.

  reply	other threads:[~2024-04-08 21:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 16:27 Christophe Lyon
2024-04-08 21:26 ` Thomas Schwinge [this message]
2024-04-29 13:24 ` Arthur Cohen
2024-04-29 13:30   ` Christophe Lyon
2024-05-02 12:54     ` Arthur Cohen

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=87edbf4kbq.fsf@euler.schwinge.ddns.net \
    --to=tschwinge@baylibre.com \
    --cc=arthur.cohen@embecosm.com \
    --cc=christophe.lyon@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=herron.philip@googlemail.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).