public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] libstdc++: testsuite: use -lbsd for net_ts on RTEMS
Date: Tue, 21 Jun 2022 00:09:22 +0000 (GMT) [thread overview]
Message-ID: <20220621000922.090FA385AE4E@sourceware.org> (raw)
https://gcc.gnu.org/g:795c4940e3233e8bb75cf8d31976d4591e827079
commit 795c4940e3233e8bb75cf8d31976d4591e827079
Author: Alexandre Oliva <oliva@adacore.com>
Date: Mon Jun 20 20:44:05 2022 -0300
libstdc++: testsuite: use -lbsd for net_ts on RTEMS
Networking functions that net_ts tests rely on are defined in libbsd
on RTEMS, so link with it.
for libstdc++-v3/ChangeLog
* testsuite/lib/dg-options.exp (add_options_for_net_ts): Add
-lbsd for RTEMS targets.
TN: V617-002
Diff:
---
libstdc++-v3/testsuite/lib/dg-options.exp | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/libstdc++-v3/testsuite/lib/dg-options.exp b/libstdc++-v3/testsuite/lib/dg-options.exp
index 203bb0dfed5..15f37da468a 100644
--- a/libstdc++-v3/testsuite/lib/dg-options.exp
+++ b/libstdc++-v3/testsuite/lib/dg-options.exp
@@ -253,6 +253,12 @@ proc add_options_for_net_ts { flags } {
# libsocket and libnsl for networking applications.
if { [istarget *-*-solaris2*] } {
return "$flags -lsocket -lnsl"
+ } elseif { [istarget *-*-rtems*] } {
+ # Adding -Wl,--gc-sections would enable a few more tests to
+ # link, but all of them fail at runtime anyway, because the
+ # io_context ctor calls pipe(), which always fails, and thus
+ # the ctor throws a system error.
+ return "$flags -lbsd"
}
return $flags
}
next reply other threads:[~2022-06-21 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 0:09 Alexandre Oliva [this message]
2022-06-21 0:17 Alexandre Oliva
2022-06-22 5:22 Alexandre Oliva
2022-06-23 5:10 Alexandre Oliva
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=20220621000922.090FA385AE4E@sourceware.org \
--to=aoliva@gcc.gnu.org \
--cc=gcc-cvs@gcc.gnu.org \
--cc=libstdc++-cvs@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).