public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/100285] experimental/net/socket/socket_base.cc fails on arm-eabi (r12-137) Date: Thu, 29 Jun 2023 23:01:10 +0000 [thread overview] Message-ID: <bug-100285-4-pZvCVXJnpj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100285-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100285 --- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:132015b9c6c9f9156ff31f7d66ba92cf01d0bc90 commit r13-7508-g132015b9c6c9f9156ff31f7d66ba92cf01d0bc90 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Jun 9 12:15:21 2023 +0100 libstdc++: Add preprocessor checks to <experimental/internet> [PR100285] We can't define endpoints and resolvers without the relevant OS support. If IPPROTO_TCP and IPPROTO_UDP are both undefined then we won't need basic_endpoint and basic_resolver anyway, so make them depend on those macros. libstdc++-v3/ChangeLog: PR libstdc++/100285 * include/experimental/internet [IPPROTO_TCP || IPPROTO_UDP] (basic_endpoint, basic_resolver_entry, resolver_base) (basic_resolver_results, basic_resolver): Only define if the tcp or udp protocols will be defined. (cherry picked from commit 793ed718b522b15e2d758eca953feeec1979fe2c)
next prev parent reply other threads:[~2023-06-29 23:01 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-27 9:53 [Bug libstdc++/100285] New: " clyon at gcc dot gnu.org 2021-04-27 13:09 ` [Bug libstdc++/100285] " cvs-commit at gcc dot gnu.org 2021-04-27 13:11 ` redi at gcc dot gnu.org 2021-04-30 12:23 ` clyon at gcc dot gnu.org 2021-04-30 13:47 ` cvs-commit at gcc dot gnu.org 2021-08-24 14:21 ` redi at gcc dot gnu.org 2021-08-24 16:00 ` cvs-commit at gcc dot gnu.org 2021-08-24 16:01 ` cvs-commit at gcc dot gnu.org 2021-08-25 16:20 ` clyon at gcc dot gnu.org 2021-08-26 11:44 ` cvs-commit at gcc dot gnu.org 2021-08-26 11:46 ` redi at gcc dot gnu.org 2021-10-12 19:41 ` cvs-commit at gcc dot gnu.org 2021-10-12 20:09 ` redi at gcc dot gnu.org 2021-10-13 8:17 ` clyon at gcc dot gnu.org 2023-06-09 12:18 ` cvs-commit at gcc dot gnu.org 2023-06-09 12:19 ` redi at gcc dot gnu.org 2023-06-29 23:01 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-15 14:36 ` redi at gcc dot gnu.org
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=bug-100285-4-pZvCVXJnpj@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).