From: Andreas Schwab <schwab@linux-m68k.org>
To: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/4] stdio: Remove the usage of $(fno-unit-at-a-time) for errlist.c
Date: Thu, 12 May 2022 09:44:58 +0200 [thread overview]
Message-ID: <87ee0znqit.fsf@igel.home> (raw)
In-Reply-To: <20220511195457.410681-3-adhemerval.zanella@linaro.org> (Adhemerval Zanella via Libc-alpha's message of "Wed, 11 May 2022 16:54:55 -0300")
On Mai 11 2022, Adhemerval Zanella via Libc-alpha wrote:
> @@ -246,6 +251,17 @@ tests-special += $(objpfx)tst-errno-manual.out
>
> include ../Rules
>
> +$(objpfx)errlist-data-aux.os: errlist-data-gen.c
> + $(make-target-directory)
> + $(compile-command.c) $(no-stack-protector) -S
> +
> +$(objpfx)errlist-data-aux.o: errlist-data-gen.c
> + $(make-target-directory)
> + $(compile-command.c) $(no-stack-protector) -S
Please rename the targets so that they don't use misleading extensions.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-05-12 7:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 19:54 [PATCH 0/4] Remove fno_unit_at_a_time configure check Adhemerval Zanella
2022-05-11 19:54 ` [PATCH 1/4] Add declare_object_symbol_alias for assembly codes (BZ #28128) Adhemerval Zanella
2022-05-11 19:54 ` [PATCH 2/4] stdio: Remove the usage of $(fno-unit-at-a-time) for errlist.c Adhemerval Zanella
2022-05-12 6:27 ` Fangrui Song
2022-05-12 7:44 ` Andreas Schwab [this message]
2022-05-11 19:54 ` [PATCH 3/4] stdio: Remove the usage of $(fno-unit-at-a-time) for siglist.c Adhemerval Zanella
2022-05-11 19:54 ` [PATCH 4/4] Remove configure fno_unit_at_a_time Adhemerval Zanella
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=87ee0znqit.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=libc-alpha@sourceware.org \
/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).