From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: Re: can i delete libtool / shared library support ?
Date: Mon, 7 Feb 2022 05:30:48 -0500 [thread overview]
Message-ID: <YgD02JQx4h5iULWe@vapier> (raw)
In-Reply-To: <YgDl9AhBMitaTYBd@vapier>
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
On 07 Feb 2022 04:27, Mike Frysinger wrote:
> let's talk about the shared library support in newlib. i want to delete it.
to provide some numbers, deleting the i?86-pc-linux-* target (which hasn't
compiled in over 5 years and no one noticed) and libtool logic yields:
1047 files changed, 4136 insertions(+), 280998 deletions(-)
this includes deleting 857 unused files from the tree.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-07 10:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 9:27 Mike Frysinger
2022-02-07 10:30 ` Mike Frysinger [this message]
2022-02-07 11:48 ` Corinna Vinschen
2022-02-07 19:30 ` Jeff Johnston
2022-02-08 1:57 ` [PATCH 0/6] delete i?86-pc-linux-gnu & libtool support Mike Frysinger
2022-02-08 1:57 ` [PATCH 1/6] newlib: drop i?86-pc-linux-* target support Mike Frysinger
2022-02-08 1:57 ` [PATCH 2/6] newlib: punt sys/linux support Mike Frysinger
2022-02-08 1:57 ` [PATCH 3/6] newlib: drop unused iconvdata Mike Frysinger
2022-02-08 4:55 ` Joel Sherrill
2022-02-08 1:57 ` [PATCH 4/6] newlib: drop libtool support Mike Frysinger
2022-02-08 9:47 ` Corinna Vinschen
2022-02-09 0:20 ` Mike Frysinger
2022-02-09 10:54 ` Corinna Vinschen
2022-02-09 8:41 ` Brian Inglis
2022-02-09 10:55 ` Corinna Vinschen
2022-02-08 1:57 ` [PATCH 5/6] newlib: drop support for $aext Mike Frysinger
2022-02-08 1:57 ` [PATCH 6/6] newlib: drop support for $oext 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=YgD02JQx4h5iULWe@vapier \
--to=vapier@gentoo.org \
--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).