public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
	"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: testsuite: test symlnks ifdef _GLIBCXX_HAVE_SYMLINK
Date: Mon, 27 Jun 2022 14:36:22 +0100	[thread overview]
Message-ID: <CACb0b4mFMn4318d7CDY_QkNYq_P0sZt00QXng-QAqV=UF6pg1w@mail.gmail.com> (raw)
In-Reply-To: <oro7yexmjc.fsf@lxoliva.fsfla.org>

On Mon, 27 Jun 2022 at 14:29, Alexandre Oliva <oliva@adacore.com> wrote:
>
> On Jun 23, 2022, Alexandre Oliva <oliva@adacore.com> wrote:
>
> > libstdc++: testsuite: conditionalize symlink tests
>
>
> libstdc++: testsuite: conditionalize another symlink test
>
> In the recent patch that introduced NO_SYMLINKS, I missed one of the
> testcases that created symlinks.
>
> Regstrapped on x86_64-linux-gnu, also tested with a cross to
> aarch64-rtems6.  Ok to install?

OK.


>
>
>
> for  libstdc++-v3/ChangeLog
>
>         * testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc
>         (test06): Don't create symlinks when NO_SYMLINKS is defined.
> ---
>  .../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 e67e2cf38f754..e2f3613a3d07e 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");
>
>
> --
> 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>
>


      reply	other threads:[~2022-06-27 13:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  6:13 Alexandre Oliva
2022-06-22  9:25 ` Jonathan Wakely
2022-06-22 10:42   ` Jonathan Wakely
2022-06-23  3:41     ` Alexandre Oliva
2022-06-23 10:53   ` Alexandre Oliva
2022-06-23 11:39     ` Jonathan Wakely
2022-06-23 11:02   ` Alexandre Oliva
2022-06-23 11:28     ` Jonathan Wakely
2022-06-23 11:29       ` Jonathan Wakely
2022-06-23 12:35       ` Alexandre Oliva
2022-06-23 12:37         ` Jonathan Wakely
2022-06-24  2:32         ` Alexandre Oliva
2022-06-27 13:29         ` Alexandre Oliva
2022-06-27 13:36           ` Jonathan Wakely [this message]

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='CACb0b4mFMn4318d7CDY_QkNYq_P0sZt00QXng-QAqV=UF6pg1w@mail.gmail.com' \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=oliva@adacore.com \
    /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).