From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] newlib: separate out libg from libc
Date: Thu, 17 Feb 2022 15:08:34 +0100 [thread overview]
Message-ID: <Yg5W4hvH79lXKfdE@calimero.vinschen.de> (raw)
In-Reply-To: <20220217044532.10798-1-vapier@gentoo.org>
On Feb 16 23:45, Mike Frysinger wrote:
> Make this a separate target from libc so that we can migrate libc over
> to automake more easily. Having it integrated into the libc target is
> difficult to handle when using automake rules which expect a one-to-one
> mapping between names & inputs.
> ---
> newlib/Makefile.am | 13 +++++++++----
> newlib/Makefile.in | 21 +++++++++++----------
> 2 files changed, 20 insertions(+), 14 deletions(-)
LGTM,
Corinna
next prev parent reply other threads:[~2022-02-17 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 4:45 Mike Frysinger
2022-02-17 14:08 ` Corinna Vinschen [this message]
2022-02-24 3:06 ` [PATCH/committed] newlib: fix multilib libg.a parallel builds Mike Frysinger
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=Yg5W4hvH79lXKfdE@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@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).