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 r13-1293] libstdc++: testsuite: conditionalize another symlink test
Date: Mon, 27 Jun 2022 13:35:05 +0000 (GMT)	[thread overview]
Message-ID: <20220627133505.0D0F838418A0@sourceware.org> (raw)

https://gcc.gnu.org/g:ca35ebaec8369b0c722d82e1f81687ba52a6e43f

commit r13-1293-gca35ebaec8369b0c722d82e1f81687ba52a6e43f
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Jun 27 10:34:15 2022 -0300

    libstdc++: testsuite: conditionalize another symlink test
    
    In the recent patch that introduced NO_SYMLINKS, I missed one of the
    testcases that created symlinks.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc
            (test06): Don't create symlinks when NO_SYMLINKS is defined.

Diff:
---
 .../27_io/filesystem/iterators/recursive_directory_iterator.cc          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc b/libstdc++-v3/testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc
index e67e2cf38f7..e2f3613a3d0 100644
--- a/libstdc++-v3/testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc
+++ b/libstdc++-v3/testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc
@@ -187,7 +187,7 @@ test05()
 void
 test06()
 {
-#if !(defined __MINGW32__ || defined __MINGW64__)
+#ifndef NO_SYMLINKS
   auto p = __gnu_test::nonexistent_path();
   create_directories(p/"d1/d2");
   create_directory_symlink("d1", p/"link");


                 reply	other threads:[~2022-06-27 13:35 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=20220627133505.0D0F838418A0@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).