From: Alexandre Oliva <oliva@adacore.com>
To: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: [PATCH] libstdc++: testsuite: use -lbsd for net_ts on RTEMS
Date: Wed, 22 Jun 2022 02:24:19 -0300 [thread overview]
Message-ID: <orczf1b798.fsf@lxoliva.fsfla.org> (raw)
Networking functions that net_ts tests rely on are defined in libbsd
on RTEMS, so link with it.
Regstrapped on x86_64-linux-gnu, also tested with a cross to
aarch64-rtems6. Ok to install?
for libstdc++-v3/ChangeLog
* testsuite/lib/dg-options.exp (add_options_for_net_ts): Add
-lbsd for RTEMS targets.
---
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 203bb0dfed505..15f37da468a5b 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
}
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next reply other threads:[~2022-06-22 5:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 5:24 Alexandre Oliva [this message]
2022-06-22 9:11 ` Jonathan Wakely
2022-06-23 9:01 ` Sebastian Huber
2022-06-23 9:06 ` Jonathan Wakely
2022-06-23 11:26 ` Alexandre Oliva
2022-06-23 11:40 ` Jonathan Wakely
2022-06-23 12:39 ` Alexandre Oliva
2022-06-27 13:29 ` 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=orczf1b798.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).