This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problems Running Testsuite

Scribbling feverishly on May 13, Gerald Pfeifer managed to emit:
> On Mon, 6 May 2002, Paolo Carlini wrote:
> >>WARNING: Couldn't find the global config file.
> >>WARNING: Couldn't find tool init file
> >>
> >>Are these important warnings that some how invalidate the results of the
> >>testsuite or may I safely disregard them?
> > The latter, AFAIK.
> Perhaps somone could contribute a patch to gcc/doc/install.texi that
> mentions this in the "Installing GCC: Testing" section? ;-)

I'll bite. How about:

----- cut here-----
$ diff -up gcc/doc/install.texi gcc/doc/
--- gcc/doc/install.texi	Sat May 11 00:42:54 2002
+++ gcc/doc/	Mon May 13 21:52:20 2002
@@ -1167,6 +1167,12 @@ The testing process will try to test as 
 distribution as possible, including the C, C++, Objective-C and Fortran
 compilers as well as the C++ and Java runtime libraries.
+While running the testsuite, DejaGnu might emit messages resembling
+@samp{WARNING: Couldn't find the global config file.} or 
+@samp{WARNING: Couldn't find tool init file}.  Although annoying,
+these messages are harmless and do not affect the validity of the
 @section How can I run the test suite on selected tests?
 As a first possibility to cut down the number of tests that are run it is
----- cut here-----

This is against the mainline cvs. I have no idea if "@samp{mumble}" is the
correct Texinfo markup...

Now I lay me down to sleep
I pray the double lock will keep;
May no brick through the window break,
And, no one rob me till I awake.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]