From: "Terry Guo" <terry.guo@arm.com>
To: "'Andreas Schwab'" <schwab@linux-m68k.org>
Cc: <gcc@gcc.gnu.org>, <libstdc++@gcc.gnu.org>
Subject: RE: Strange behavior of libstdc++ regression test
Date: Thu, 19 Apr 2012 08:01:00 -0000 [thread overview]
Message-ID: <000c01cd1e02$c0ac5620$42050260$@guo@arm.com> (raw)
In-Reply-To: <m262cw424m.fsf@igel.home>
>
> "Terry Guo" <terry.guo@arm.com> writes:
>
> > make[1]: *** [check-recursive] Error 1
> > make[1]: Target `check' not remade because of errors.
> > make[1]: Leaving directory
> > `/home/build/gcc-4-7-daily-test/build-linux/gcc-final/arm-none-
> eabi/libstdc+
> > +-v3'
> > make: *** [check-target-libstdc++-v3] Error 2
> > make: Target `check-target' not remade because of errors.
>
> You had unexpected failures/successes. Look at the first error, not
> the
> last one.
>
Ah, you are right. I just thought the "make -k" should keep going and omit
all the errors. Now I think I should use "make -k -i" to do it. Thanks for
the help.
BR,
Terry
next prev parent reply other threads:[~2012-04-19 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14015.132308896$1334819010@news.gmane.org>
2012-04-19 7:23 ` Andreas Schwab
2012-04-19 8:01 ` Terry Guo [this message]
2012-04-19 8:42 ` Andreas Schwab
2012-04-19 7:04 Terry Guo
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='000c01cd1e02$c0ac5620$42050260$@guo@arm.com' \
--to=terry.guo@arm.com \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=schwab@linux-m68k.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).