From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH 0/7] Sync top-level files for libtool.m4 updates
Date: Fri, 7 Jan 2022 10:59:26 +0100 [thread overview]
Message-ID: <YdgO/iA7KMqVh+R5@calimero.vinschen.de> (raw)
In-Reply-To: <20220101200554.16454-1-vapier@gentoo.org>
On Jan 1 15:05, Mike Frysinger wrote:
> I've extracted commits made to the binutils/gdb tree to bring libtool.m4
> up-to-date (as well as some supplemental files for newer autotools).
> This will allow updating to newer autoconf & automake and fix some new
> warnings as a result.
>
> I haven't included the regenerated autotool files here since I'm juggling
> a bunch of changes and they're all leading to conflicts. I'll make sure
> to include those before actually pushing anything. I have tested that I
> can actually regenerate & rebuild things already.
>
> Alexander von Gluck IV (1):
> Add support for the haiku operating system. These are the os support
> patches we have been grooming and maintaining for quite a few years
> over on git.haiku-os.org. All of these architectures are working and
> most have been stable for quite some time.
>
> H.J. Lu (2):
> GCC: Pass --plugin to AR and RANLIB
> GCC: Check if AR works with --plugin and rc
>
> Nick Alcock (2):
> libtool.m4: augment symcode for Solaris 11
> libtool.m4: fix nm BSD flag detection
>
> Samuel Thibault (1):
> libtool.m4: update GNU/Hurd test from upstream. In upstream libtool,
> 47a889a4ca20 ("Improve GNU/Hurd support.") fixed detection of
> shlibpath_overrides_runpath, thus avoiding unnecessary relink. This
> backports it.
>
> Simon Marchi (1):
> Bump to autoconf 2.69 and automake 1.15.1
>
> .gitignore | 1 -
> Makefile.in | 5 +-
> Makefile.tpl | 5 +-
> README-maintainer-mode | 4 +-
> ar-lib | 270 +++++++++
> config/gcc-plugin.m4 | 40 ++
> config/override.m4 | 2 +-
> configure | 1238 +++++++++++++++++++++-------------------
> configure.ac | 22 +-
> libtool.m4 | 140 +++--
> test-driver | 148 +++++
> 11 files changed, 1226 insertions(+), 649 deletions(-)
> create mode 100755 ar-lib
> create mode 100755 test-driver
>
> --
> 2.33.0
Ok, please push.
Thanks,
Corinna
prev parent reply other threads:[~2022-01-07 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 20:05 Mike Frysinger
2022-01-01 20:05 ` [PATCH 1/7] Bump to autoconf 2.69 and automake 1.15.1 Mike Frysinger
2022-01-01 20:05 ` [PATCH 2/7] libtool.m4: update GNU/Hurd test from upstream. In upstream libtool, 47a889a4ca20 ("Improve GNU/Hurd support.") fixed detection of shlibpath_overrides_runpath, thus avoiding unnecessary relink. This backports it Mike Frysinger
2022-01-01 20:05 ` [PATCH 3/7] GCC: Pass --plugin to AR and RANLIB Mike Frysinger
2022-01-01 20:05 ` [PATCH 4/7] GCC: Check if AR works with --plugin and rc Mike Frysinger
2022-01-01 20:05 ` [PATCH 5/7] Add support for the haiku operating system. These are the os support patches we have been grooming and maintaining for quite a few years over on git.haiku-os.org. All of these architectures are working and most have been stable for quite some time Mike Frysinger
2022-01-01 20:05 ` [PATCH 6/7] libtool.m4: augment symcode for Solaris 11 Mike Frysinger
2022-01-01 20:05 ` [PATCH 7/7] libtool.m4: fix nm BSD flag detection Mike Frysinger
2022-01-07 9:59 ` 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=YdgO/iA7KMqVh+R5@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).