From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH 0/8] newlib: convert newlib.h to autoheader
Date: Wed, 19 Jan 2022 15:51:32 +0100 [thread overview]
Message-ID: <YegldBzKQcn80eMT@calimero.vinschen.de> (raw)
In-Reply-To: <20220118044741.21027-1-vapier@gentoo.org>
On Jan 17 23:47, Mike Frysinger wrote:
> This is a series of cleanups to make newlib.hin be managed automatically
> by autoheader instead of being hand maintained. This will also make the
> standard autoreconf command not fall over due to the current poor state
> of the header files, as well as not make it corrupt/clobber the version
> header file.
>
> I've split these up to (hopefully) make it easier to review, and be easy
> to merge most of them independently. If there is some reason we don't
> want to actually leverage autoheader, or maybe we want to rework how the
> final step is done, we can still land the rest of the stack while that
> discussion is ongoing.
>
> Mike Frysinger (8):
> newlib: internalize HAVE_INITFINI_ARRAY
> newlib: merge acconfig.h changes into newlib.hin
> newlib: clean up autoheader templates
> newlib: sort newlib.h output
> newlib: move version defines out of the config headers
> newlib: add missing _NANO_MALLOC to newlib.hin
> newlib: iconv: autogenerate iconv define list
> newlib: switch newlib.h to autoheader
>
> newlib/Makefile.in | 34 +-
> newlib/_newlib_version.hin | 16 +-
> newlib/acconfig.h | 191 --------
> newlib/aclocal.m4 | 1 +
> newlib/configure | 695 ++++++++++++++++++++++++-----
> newlib/configure.ac | 105 +++--
> newlib/configure.host | 2 +-
> newlib/iconv.m4 | 305 +++++++++++++
> newlib/libc/iconv/ces/mkdeps.pl | 39 ++
> newlib/libc/misc/fini.c | 6 +-
> newlib/libc/misc/init.c | 6 +-
> newlib/libc/stdlib/__call_atexit.c | 2 +-
> newlib/libc/sys/arm/crt0.S | 2 +-
> newlib/newlib.hin | 503 +++++++++++++++------
> 14 files changed, 1398 insertions(+), 509 deletions(-)
> delete mode 100644 newlib/acconfig.h
> create mode 100644 newlib/iconv.m4
>
> --
> 2.33.0
The patchset looks good to me. Please push.
Thanks,
Corinna
prev parent reply other threads:[~2022-01-19 14:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 4:47 Mike Frysinger
2022-01-18 4:47 ` [PATCH 1/8] newlib: internalize HAVE_INITFINI_ARRAY Mike Frysinger
[not found] ` <DM3P110MB0522248DFEE102BB37B43A8F9A589@DM3P110MB0522.NAMP110.PROD.OUTLOOK.COM>
2022-01-18 16:10 ` Fw: " C Howland
2022-01-19 0:53 ` Mike Frysinger
2022-01-19 2:39 ` C Howland
2022-01-19 3:44 ` Mike Frysinger
2022-01-19 23:50 ` Mike Frysinger
2022-01-18 4:47 ` [PATCH 2/8] newlib: merge acconfig.h changes into newlib.hin Mike Frysinger
2022-01-18 4:47 ` [PATCH 3/8] newlib: clean up autoheader templates Mike Frysinger
2022-01-18 4:47 ` [PATCH 4/8] newlib: sort newlib.h output Mike Frysinger
2022-01-18 4:47 ` [PATCH 5/8] newlib: move version defines out of the config headers Mike Frysinger
2022-01-18 4:47 ` [PATCH 6/8] newlib: add missing _NANO_MALLOC to newlib.hin Mike Frysinger
2022-01-18 4:47 ` [PATCH 7/8] newlib: iconv: autogenerate iconv define list Mike Frysinger
2022-01-18 4:47 ` [PATCH 8/8] newlib: switch newlib.h to autoheader Mike Frysinger
2022-01-19 14:51 ` 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=YegldBzKQcn80eMT@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).