From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] newlib: libc: delete crt0.o duplication
Date: Fri, 18 Feb 2022 13:33:49 +0100 [thread overview]
Message-ID: <Yg+SLXJr0WO/Zekz@calimero.vinschen.de> (raw)
In-Reply-To: <20220217050408.22442-1-vapier@gentoo.org>
On Feb 17 00:04, Mike Frysinger wrote:
> The crt0.o was handled in a subdir-by-subdir basis: it would be compiled
> in one (e.g. libc/sys/$arch/), then copied up one level (libc/sys/), then
> copied up another (libc/) before finally being copied & installed in the
> top newlib dir. The libc/sys/ copy was cleaned up, and then the top dir
> was changed to copy it directly out of the libc/sys/$arch/ dir. But the
> libc/sys/ copy to libc/ was left behind. Clean that up now too.
> ---
LGTM
Thx,
Corinna
prev parent reply other threads:[~2022-02-18 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 5:04 Mike Frysinger
2022-02-18 12:33 ` Corinna Vinschen [this message]
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=Yg+SLXJr0WO/Zekz@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).