public inbox for
 help / color / mirror / Atom feed
From: Detlef Vollmann <>
To: Jonathan Wakely <>
Cc: libstdc++ <>, gcc Patches <>
Subject: Re: [committed] libstdc++: Move closing brace outside #endif [PR104866]
Date: Fri, 11 Mar 2022 16:35:49 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]

On 3/11/22 16:12, Jonathan Wakely wrote:
> On Fri, 11 Mar 2022 at 14:28, Detlef Vollmann wrote:
>> With this and the other fix I was able to build the complete
>> libstdc++ for AVR based on AVR Libc 2.0 (plus some ad hoc
>> AVR header fixes) from git master 5e28be89.
> Nice. I finally figure out that I need to use --enable-libstdcxx *not*
> --enable-libstdc++-v3 to build for AVR,
Yes, I had the same problem.
A comment in the 'configure' script still says libstdc++-v3
and in the configure docs at
there's neither :-(

> and now I get errors due to
> EOVERFLOW being undefined. Is that what you fixed?
One of them.

> We should make that work. Arguably, all values of std::errc should
> exist, even if the OS <errno.h> doesn't provide a constant. We could
> define the missing ones ourselves, choosing numbers > 1000 (and hope
> the OS uses small numbers for its own errno values).
I simply defined all that were required.

I've attached a tarball with all my header fixes.
To get them picked up while compiling libstdc++ I had to
put them into ${prefix}/avr/lib/include.

But these are really ad hoc, some of the problems I think should
be fixed in the libstdc++ sources.
E.g. I think it's wrong to expect that specific functions are
available if a respective header is available (e.g. close()
in unistd.h).


[-- Attachment #2: avr-fixups.tar.bz2 --]
[-- Type: application/octet-stream, Size: 1321 bytes --]

  parent reply	other threads:[~2022-03-11 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 21:11 Jonathan Wakely
2022-03-11 14:27 ` Detlef Vollmann
2022-03-11 15:12   ` Jonathan Wakely
2022-03-11 15:21     ` Jonathan Wakely
2022-03-11 15:35     ` Detlef Vollmann [this message]
2022-03-11 17:59       ` Jonathan Wakely
2022-03-11 19:24         ` Detlef Vollmann
2022-03-14  9:57           ` Detlef Vollmann

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).