This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


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: Interpreting gcc-3.3 "make check" results


Ken Rose wrote:
I'm testing gcc-3.3/glibc-2.3.2, and I forgot to use the -k option
to 'make check', so it terminated on the first failure.

-k is a new one for me. When did it appear?

1985 or so. It just means 'keep running make even if one target fails'. It's used in e.g. contrib/regression/btest-gcc.sh

"man pmake" says
     -k      Continue processing after errors are encountered, but only on
             those targets that do not depend on the target whose creation
             caused the error.

Unfortunately, I don't have any magic recipe for dealing with test
failures.  It seems that you just need to look at them one at a time and
figure out what went wrong, and then decide what to do about it.

Yup. And see what others have done about 'em.


- Dan

--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045


------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


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