--- Comment #4 from pinskia at gcc dot gnu dot org 2006-04-05 19:14 ---
Always do a make check, this is the correct thing to do when checking the
compiler anyways.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #3 from tromey at gcc dot gnu dot org 2006-03-31 23:30 ---
Is there a reasonable way to detect good failures versus bad failures here?
We definitely want to ignore cases where gcj-dbtool fails due to things
like not having mmap available.
Perhaps the thing to do is let it fa
--- Comment #2 from hjl at lucon dot org 2006-01-18 19:14 ---
It depends on what kind of failure. This "Segmentation fault" is due to a
broken libgcj.so. It makes no senses to continue.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25847
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-01-18 19:00 ---
Lets look:
## We don't actually care if it fails -- if it does, just make an
## empty file. This is simpler than trying to discover when mmap is
## not available.
so what is the problem here? This is not really a
