From: "Deepak B. Nayak" <deepakbn@csa.iisc.ernet.in>
To: Jim Wilson <wilson@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: running gcc testcases
Date: Fri, 11 Oct 2002 13:59:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.96.1021012002121.28174C-100000@osiris.csa.iisc.ernet.in> (raw)
In-Reply-To: <xwuk7kpt0pn.fsf@tonopah.toronto.redhat.com>
On 11 Oct 2002, Jim Wilson wrote:
> There isn't enough info here to understand what your problem is. Exact
> commands and exact output from those commands would help. For instance,
> it isn't clear what directory you typed make in.
dir is srcdir/objdir
> It isn't clear which
> testcases you are trying to run. It isn't clear what command you used to
> run those testcases.
we just executed "make" in objdir
It isn't clear what errors you are getting from those
> commands. Etc.
>
we did not get any errors..problem was first time when we executed "make"
in objdir,it executed all the testcases(atleast it executed our pass many
times..).but then we added few more printf's in our code for clear
debugging then "make" did not run the testcases.As u said we were wrong in
running only "make" in objdir
> No testcases are run when you type make. Testcase are run only if you type
> make check, and then will be run everytime you type make check.
> The dejagnu
> package is required to run the testsuite.
we did not down load anyother package except gcc-3.0.tar.gz.we did not
download anyother package becos in install page it was given that if u
have downloaded full package (not only core compiler..)then no need to
download test cases
> I am guessing that you somehow
> confused a library build with a testsuite run. The library files won't be
> rebuilt when the compiler changes. You can force library files to be rebuilt
> by deleting them.
>
now one more problem is..
now we r using "make check" in objdir.....
when we run this second time and later..this does not consider the
changes(added printf's in the code..)but execute few testcases not as many
as in first time....
after being frustrated for some time but we have found a solution which
is not a logical one...
solution is....everytime time we make some changes to source code,then we
make simple changes to Makefile.in and run "make" in objdir..
This works fine..it executes all testcases considering all new changes...
may be this is very illogical..so please give us some solution to this
problem...
regards
deepak
> Jim
>
next prev parent reply other threads:[~2002-10-11 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 5:37 Deepak B. Nayak
2002-10-11 10:02 ` Jim Wilson
2002-10-11 13:59 ` Deepak B. Nayak [this message]
2002-10-15 15:43 ` Jim Wilson
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=Pine.SOL.3.96.1021012002121.28174C-100000@osiris.csa.iisc.ernet.in \
--to=deepakbn@csa.iisc.ernet.in \
--cc=gcc@gcc.gnu.org \
--cc=wilson@redhat.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).