From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] newlib: punt unused LIBC_EXTRA_LIB settings
Date: Fri, 21 Jan 2022 14:38:55 +0100 [thread overview]
Message-ID: <Yeq3b9AFRzUxxg+r@calimero.vinschen.de> (raw)
In-Reply-To: <20220121120557.22761-1-vapier@gentoo.org>
On Jan 21 07:05, Mike Frysinger wrote:
> This was added decades ago, but the commit message lacks any
> explanation, and it was unused when it was merged. It's still
> unused today. So punt it all.
> ---
> newlib/libc/Makefile.am | 26 ++++----------
> newlib/libc/Makefile.in | 44 +++++++-----------------
> newlib/libc/argz/Makefile.in | 3 --
> newlib/libc/configure | 15 ++------
> newlib/libc/configure.ac | 8 -----
> newlib/libc/ctype/Makefile.in | 3 --
> newlib/libc/errno/Makefile.in | 3 --
> newlib/libc/iconv/Makefile.in | 3 --
> newlib/libc/iconv/ccs/Makefile.in | 3 --
> newlib/libc/iconv/ccs/binary/Makefile.in | 3 --
> newlib/libc/iconv/ces/Makefile.in | 3 --
> newlib/libc/iconv/lib/Makefile.in | 3 --
> newlib/libc/libc.texi | 1 -
> newlib/libc/locale/Makefile.in | 3 --
> newlib/libc/misc/Makefile.in | 3 --
> newlib/libc/posix/Makefile.in | 3 --
> newlib/libc/reent/Makefile.in | 3 --
> newlib/libc/search/Makefile.in | 3 --
> newlib/libc/signal/Makefile.in | 3 --
> newlib/libc/ssp/Makefile.in | 3 --
> newlib/libc/stdio/Makefile.in | 3 --
> newlib/libc/stdio64/Makefile.in | 3 --
> newlib/libc/stdlib/Makefile.in | 3 --
> newlib/libc/string/Makefile.in | 3 --
> newlib/libc/syscalls/Makefile.in | 3 --
> newlib/libc/time/Makefile.in | 3 --
> newlib/libc/unix/Makefile.in | 3 --
> newlib/libc/xdr/Makefile.in | 3 --
> 28 files changed, 21 insertions(+), 142 deletions(-)
LGTM. Will we still have configure files when you finished? :)))
Thanks,
Corinna
next prev parent reply other threads:[~2022-01-21 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 12:05 Mike Frysinger
2022-01-21 13:38 ` Corinna Vinschen [this message]
2022-01-21 22:19 ` 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=Yeq3b9AFRzUxxg+r@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).