public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] htl/tests: Reformat Makefile.
Date: Sun, 25 Feb 2024 18:42:58 +0000 (GMT) [thread overview]
Message-ID: <20240225184258.B8B8B3858427@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5420d211f057d26d6d42724dd13c5b43fdd7a9a3
commit 5420d211f057d26d6d42724dd13c5b43fdd7a9a3
Author: Carlos O'Donell <carlos@redhat.com>
Date: Fri Jun 9 17:45:23 2023 -0400
htl/tests: Reformat Makefile.
Reflow and sort Makefile.
No code generation changes in non-test binary artifacts.
No regressions on x86_64 and i686.
Tested with build-many-glibcs.py for x86_64-gnu.
Diff:
---
htl/tests/Makefile | 23 +++++++++++++++++++----
1 file changed, 19 insertions(+), 4 deletions(-)
diff --git a/htl/tests/Makefile b/htl/tests/Makefile
index 7177ad181e..468adb58d5 100644
--- a/htl/tests/Makefile
+++ b/htl/tests/Makefile
@@ -7,9 +7,24 @@ CFLAGS=-Wall -g
LDLIBS = -lpthread
-CHECK_SRC := test-1.c test-2.c test-3.c test-6.c test-7.c test-8.c \
- test-9.c test-10.c test-11.c test-12.c test-13.c test-14.c \
- test-15.c test-16.c test-17.c test-__pthread_destroy_specific-skip.c
+CHECK_SRC := \
+ test-1.c \
+ test-10.c \
+ test-11.c \
+ test-12.c \
+ test-13.c \
+ test-14.c \
+ test-15.c \
+ test-16.c \
+ test-17.c \
+ test-2.c \
+ test-3.c \
+ test-6.c \
+ test-7.c \
+ test-8.c \
+ test-9.c \
+ test-__pthread_destroy_specific-skip.c \
+ # CHECK_SRC
CHECK_OBJS := $(addsuffix .o,$(basename $(notdir $(CHECK_SRC))))
CHECK_PROGS := $(basename $(notdir $(CHECK_SRC))) \
@@ -37,4 +52,4 @@ check: $(CHECK_OBJS) $(CHECK_PROGS)
clean:
rm -f $(CHECK_OBJS) $(CHECK_PROGS) \
- $(addsuffix .out,$(basename $(notdir $(CHECK_PROGS))))
\ No newline at end of file
+ $(addsuffix .out,$(basename $(notdir $(CHECK_PROGS))))
reply other threads:[~2024-02-25 18:42 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=20240225184258.B8B8B3858427@sourceware.org \
--to=carlos@sourceware.org \
--cc=glibc-cvs@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).