public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: H.J. Lu <hjl@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] sysdeps/unix/sysv/linux/x86_64/Makefile: Add the end marker
Date: Wed, 28 Feb 2024 13:48:46 +0000 (GMT)	[thread overview]
Message-ID: <20240228134847.051A53858C31@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=e6350be7e9cae8f71c96c1f06eab61b9acb227c8

commit e6350be7e9cae8f71c96c1f06eab61b9acb227c8
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Wed Feb 28 05:46:40 2024 -0800

    sysdeps/unix/sysv/linux/x86_64/Makefile: Add the end marker
    
    Add the end marker to tests, tests-container and modules-names.

Diff:
---
 sysdeps/unix/sysv/linux/x86_64/Makefile | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/sysdeps/unix/sysv/linux/x86_64/Makefile b/sysdeps/unix/sysv/linux/x86_64/Makefile
index 4223feb95f..7d1d205fa0 100644
--- a/sysdeps/unix/sysv/linux/x86_64/Makefile
+++ b/sysdeps/unix/sysv/linux/x86_64/Makefile
@@ -17,18 +17,21 @@ endif
 ifeq ($(subdir),elf)
 ifeq (yes,$(enable-x86-isa-level))
 tests += \
-  tst-glibc-hwcaps-2
+  tst-glibc-hwcaps-2 \
+# tests
 ifeq (no,$(build-hardcoded-path-in-tests))
 # This is an ld.so.cache test, and RPATH/RUNPATH in the executable
 # interferes with its test objectives.
 tests-container += \
-  tst-glibc-hwcaps-2-cache
+  tst-glibc-hwcaps-2-cache \
+# tests-container
 endif
 modules-names += \
   libx86-64-isa-level-1 \
   libx86-64-isa-level-2 \
   libx86-64-isa-level-3 \
-  libx86-64-isa-level-4
+  libx86-64-isa-level-4 \
+# modules-names
 
 $(objpfx)tst-glibc-hwcaps-2: $(objpfx)libx86-64-isa-level.so

                 reply	other threads:[~2024-02-28 13:48 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=20240228134847.051A53858C31@sourceware.org \
    --to=hjl@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).