public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r10-9611] libstdc++: Fix test failure on AIX
Date: Mon, 29 Mar 2021 20:04:53 +0000 (GMT)	[thread overview]
Message-ID: <20210329200453.EA84F3861013@sourceware.org> (raw)

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

commit r10-9611-gad70672e19712c480c138f8c3823f7566fe4e5f8
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Nov 25 16:58:05 2020 +0000

    libstdc++: Fix test failure on AIX
    
    This fixes a failure on AIX 7.2:
    
    FAIL: 17_intro/names.cc (test for excess errors)
    Excess errors:
    /home/jwakely/src/gcc/libstdc++-v3/testsuite/17_intro/names.cc:99: error: expected identifier before '(' token
    /usr/include/sys/var.h:187: error: expected unqualified-id before '{' token
    /usr/include/sys/var.h:187: error: expected ')' before '{' token
    /usr/include/sys/var.h:337: error: expected unqualified-id before ';' token
    /usr/include/sys/var.h:337: error: expected ')' before ';' token
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/17_intro/names.cc: Do not test 'v' on AIX.
    
    (cherry picked from commit 1a8d1f54de371de88b2604d8c0e4e01306be8870)

Diff:
---
 libstdc++-v3/testsuite/17_intro/names.cc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/libstdc++-v3/testsuite/17_intro/names.cc b/libstdc++-v3/testsuite/17_intro/names.cc
index 5a61c97e989..2c8bfff26e1 100644
--- a/libstdc++-v3/testsuite/17_intro/names.cc
+++ b/libstdc++-v3/testsuite/17_intro/names.cc
@@ -193,6 +193,8 @@
 #undef r
 #undef x
 #undef y
+// <sys/var.h> defines vario::v
+#undef v
 #endif
 
 #ifdef __hpux__


                 reply	other threads:[~2021-03-29 20:04 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=20210329200453.EA84F3861013@sourceware.org \
    --to=redi@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).