From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH 2/2] ctype: use less short names in public header
Date: Fri, 3 Dec 2021 10:56:04 +0100 [thread overview]
Message-ID: <YanptF788ul5pev+@calimero.vinschen.de> (raw)
In-Reply-To: <YaiffFJRea7LUgKq@calimero.vinschen.de>
On Dec 2 11:27, Corinna Vinschen wrote:
> On Nov 30 17:52, Richard Earnshaw wrote:
> > On 30/11/2021 17:15, Jonathan Wakely wrote:
> > > On Tue, 30 Nov 2021 at 17:12, Jonathan Wakely <jwakely@redhat.com> wrote:
> > > >
> > > > On Tue, 30 Nov 2021 at 15:14, Corinna Vinschen <vinschen@redhat.com> wrote:
> > > > > Is there a good reason to revert these patches in newlib? I see the
> > > > > problem but I'm unclear on how problematic the change is in real life.
> > > >
> > > > You cannot use newlib from Git to build any released version of GCC.
> > > >
> > > > Is building newlib from Git only supported when using GCC trunk, or is
> > >
> > > Oops, I mean building *against* newlib from Git, not building newlib
> > > itself. You can still build newlib itself, because it doesn't use C++.
> > > But you can't build a GCC 11.2.0 compiler that uses the latest newlib
> > > from Git as its libc.
> > >
> > > > it supposed to build with e.g. GCC 11.2.0 from July this year? If yes,
> > > > then newlib needs changes (whether reverting the change entirely, or
> > > > just making another change to restore the old names in addition to the
> > > > new ones).
> > >
> >
> > My concern is that the proposed workaround may break other (probably buggy)
> > apps that have been relying on the old BSD internal API for 30 odd years.
> > The proposed workaround only solves the issue for G++.
>
> I'm inclined to revert 3ba1bd0d9db, given it solves a problem which
> isn't actually a problem in newlib, but in an application not following
> the standards in terms of reserved symbols.
>
> I'm discussing this with Jeff, stay tuned.
Reverted.
Corinna
next prev parent reply other threads:[~2021-12-03 9:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 0:21 what's up with _COMPILING_NEWLIB Mike Frysinger
2021-11-08 10:05 ` Corinna Vinschen
2021-11-08 11:46 ` Mike Frysinger
2021-11-08 15:05 ` Corinna Vinschen
2021-11-08 18:14 ` Mike Frysinger
2021-11-09 1:24 ` [PATCH 1/2] define _COMPILING_NEWLIB for all targets when compiling Mike Frysinger
2021-11-09 1:24 ` [PATCH 2/2] ctype: use less short names in public header Mike Frysinger
2021-11-09 11:38 ` Corinna Vinschen
2021-11-10 0:18 ` Mike Frysinger
2021-11-10 10:56 ` Corinna Vinschen
2021-11-30 12:18 ` Jonathan Wakely
2021-11-11 1:37 ` [PATCH v2] " Mike Frysinger
2021-11-11 10:35 ` Corinna Vinschen
2021-11-11 22:28 ` Mike Frysinger
2021-11-12 10:27 ` Corinna Vinschen
2021-11-20 20:08 ` Brian Inglis
2021-11-23 15:09 ` [PATCH 2/2] " Richard Earnshaw
2021-11-24 4:15 ` Mike Frysinger
2021-11-24 10:58 ` Richard Earnshaw
2021-11-24 11:01 ` Richard Earnshaw
2021-11-30 12:01 ` Jonathan Wakely
2021-11-30 15:14 ` Corinna Vinschen
2021-11-30 17:12 ` Jonathan Wakely
2021-11-30 17:15 ` Jonathan Wakely
2021-11-30 17:52 ` Richard Earnshaw
2021-12-02 10:27 ` Corinna Vinschen
2021-12-03 9:56 ` Corinna Vinschen [this message]
2021-12-05 9:42 ` 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=YanptF788ul5pev+@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).