From: Ian Lance Taylor <iant@google.com>
To: Prathamesh Kulkarni <bilbotheelffriend@gmail.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: make -k check error
Date: Fri, 17 Jan 2014 18:57:00 -0000 [thread overview]
Message-ID: <CAKOQZ8zyO=j7iB0Pz7+oQk3Wv2y=776-6PaLfrZ4rjXEZS81Vw@mail.gmail.com> (raw)
In-Reply-To: <CAJXstsDS5-P7Lgyp=8CX=pAR+n-Ka8sz0LCzFVV6iqmz_H5RXQ@mail.gmail.com>
On Fri, Jan 17, 2014 at 9:33 AM, Prathamesh Kulkarni
<bilbotheelffriend@gmail.com> wrote:
> Hi, after building gcc-4.9.0 with make bootstrap, i ran
> make -k check and got the following error (make bootstrap, make
> install work smoothly):
>
> make[3]: [check-parallel-gcc] Error 1 (ignored)
> make[4]: *** [check-DEJAGNU] Error 1
> make[3]: *** [check-am] Error 2
> make[3]: Target `check' not remade because of errors.
> make[2]: *** [check-recursive] Error 1
> make[2]: Target `check' not remade because of errors.
> make[1]: *** [check-target-libjava] Error 2
> make[4]: *** [check-DEJAGNU] Error 1
> make[3]: *** [check-am] Error 2
> make[3]: Target `check' not remade because of errors.
> make[2]: *** [check-recursive] Error 1
> make[2]: Target `check' not remade because of errors.
> make[1]: *** [check-target-libgomp] Error 2
> make[1]: Target `check-target' not remade because of errors.
> make: *** [do-check] Error 2
> make: Target `check' not remade because of errors.
All this tells us is that some tests failed. That is fairly normal.
You will have to actually look at the test failures to see what
happened.
Ian
next prev parent reply other threads:[~2014-01-17 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 17:34 Prathamesh Kulkarni
2014-01-17 18:57 ` Ian Lance Taylor [this message]
2014-01-17 19:01 ` David Kredba
2014-01-18 6:48 ` Prathamesh Kulkarni
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='CAKOQZ8zyO=j7iB0Pz7+oQk3Wv2y=776-6PaLfrZ4rjXEZS81Vw@mail.gmail.com' \
--to=iant@google.com \
--cc=bilbotheelffriend@gmail.com \
--cc=gcc-help@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).