From: fweimer@redhat.com (Florian Weimer)
To: libc-alpha@sourceware.org
Subject: [PATCH COMMITTED] inet: Actually build and run tst-deadline
Date: Wed, 04 Apr 2018 14:12:00 -0000 [thread overview]
Message-ID: <20180404141206.CA9B5404417ED@oldenburg.str.redhat.com> (raw)
2018-04-04 Florian Weimer <fweimer@redhat.com>
inet: Actually build and run tst-deadline.
* inet/Makefile (tests-internal): Add tst-deadline and do not
overwrite the variable.
(tests-static-internal): Remove variable.
diff --git a/inet/Makefile b/inet/Makefile
index f63c7e25ba..5d02c37626 100644
--- a/inet/Makefile
+++ b/inet/Makefile
@@ -57,11 +57,11 @@ tests := htontest test_ifindex tst-ntoa tst-ether_aton tst-network \
# tst-deadline must be linked statically so that we can access
# internal functions.
tests-static += tst-deadline
-tests-static-internal := tst-deadline
+tests-internal += tst-deadline
# tst-inet6_scopeid_pton also needs internal functions but does not
# need to be linked statically.
-tests-internal := tst-inet6_scopeid_pton
+tests-internal += tst-inet6_scopeid_pton
include ../Rules
reply other threads:[~2018-04-04 14:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180404141206.CA9B5404417ED@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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).