From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
Cesar Philippidis <cesar@codesourcery.com>,
Jonathan Wakely <jwakely@redhat.com>,
Sandra Loosemore <sandra@codesourcery.com>,
"libstdc++" <libstdc++@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch ping] libstdc++ testsuite cxxflags
Date: Fri, 30 May 2014 07:53:00 -0000 [thread overview]
Message-ID: <CAJA7tRb=t9U64RLtp9tNeJSwaQfYc09Tz2R0eD5bYuD4odcxPA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRK6Wo2MpSA0bYy9W9JVed3SG77QVTdUOmOHGdsoX+QoA@mail.gmail.com>
On Sat, May 24, 2014 at 5:54 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 24 May 2014 17:07, David Edelsohn wrote:
>> This patch broke the ability to run the libstdc++ testsuite on AIX.
>>
>> I now see the following errors:
>>
>> bad switch "-O": must be -all, -about, -indices, -inline, -expanded, -line, -lin
>> estop, -lineanchor, -nocase, -start, or --
>> while executing
>> "regexp "\-O" $cxxflags"
>
> Would this work instead?
>
> regexp ".*-O" $cxxflags
With all the other build breakages in the past week, I've just
started seeing the first set of testresults from an auto-tester. It
looks like on a cross test using rhe5 / x86_64 with the version of
tcl8.4 I'm using I see the same errors that David saw.
The testsuite starts running if I tried the above
regexp ".*-O" $cxxflags
Is this going to be applied - what gives ?
regards
Ramana
next prev parent reply other threads:[~2014-05-30 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 16:07 David Edelsohn
2014-05-24 16:54 ` Jonathan Wakely
2014-05-25 19:16 ` David Edelsohn
2014-05-30 7:53 ` Ramana Radhakrishnan [this message]
2014-05-30 11:11 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2014-05-17 0:16 Sandra Loosemore
2014-05-17 4:56 ` Mike Stump
2014-05-17 9:50 ` Jonathan Wakely
2014-05-17 9:52 ` Jonathan Wakely
2014-05-17 10:07 ` Jonathan Wakely
2014-05-19 20:57 ` Sandra Loosemore
2014-05-20 9:11 ` Jonathan Wakely
2014-05-20 19:38 ` Cesar Philippidis
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='CAJA7tRb=t9U64RLtp9tNeJSwaQfYc09Tz2R0eD5bYuD4odcxPA@mail.gmail.com' \
--to=ramana.gcc@googlemail.com \
--cc=cesar@codesourcery.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=ramrad01@arm.com \
--cc=sandra@codesourcery.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).