public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon 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: Fri, 30 Apr 2021 12:23:26 +0000 [thread overview]
Message-ID: <bug-100285-4-YKlQ8lZPjQ@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
Christophe Lyon <clyon at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2021-04-30
Status|UNCONFIRMED |NEW
--- Comment #3 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Not quite, I'm now seeing:
In file included from
/libstdc++-v3/testsuite/experimental/net/socket/socket_base.cc:20:
/aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-arm-none-eabi/gcc3/arm-none-eabi/libstdc++-v3/include/experimental/socket:
In member function 'void
std::experimental::net::v1::__basic_socket_impl<_Protocol>::set_option(const
_SettableSocketOption&, std::error_code&)':
/aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-arm-none-eabi/gcc3/arm-none-eabi/libstdc++-v3/include/experimental/socket:625:
error: '::setsockopt' has not been declared
/aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-arm-none-eabi/gcc3/arm-none-eabi/libstdc++-v3/include/experimental/socket:
In member function 'void
std::experimental::net::v1::__basic_socket_impl<_Protocol>::get_option(_GettableSocketOption&,
std::error_code&) const':
/aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-arm-none-eabi/gcc3/arm-none-eabi/libstdc++-v3/include/experimental/socket:639:
error: '::getsockopt' has not been declared; did you mean 'getsubopt'?
/aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-arm-none-eabi/gcc3/arm-none-eabi/libstdc++-v3/include/experimental/socket:
In member function 'void
std::experimental::net::v1::__basic_socket_impl<_Protocol>::_M_close()':
/aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-arm-none-eabi/gcc3/arm-none-eabi/libstdc++-v3/include/experimental/socket:709:
error: 'linger' is not a member of 'std::experimental::net::v1::socket_base'
[....]
next prev parent reply other threads:[~2021-04-30 12:23 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 [this message]
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
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-YKlQ8lZPjQ@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: 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).