While investigating PR 25840, I notice that when there is a fatal error during
libjava build, build doesn't stop. I found this in my build log:
creating gcj-dbtool ./gcj-dbtool -n classmap.db || touch classmap.db
creating gij /bin/sh: line 1: 17842 Segmentation fault ./gcj-dbtool -n
classmap.db
make[5]: Leaving directory
`/export/build/gnu/gcc-next/build-x86_64-linux/x86_64-unknown-linux-gnu/libjava'
The problem is in libjava/Makefile.am:
## The .db file. This rule is only used for native builds, so it is
## safe to invoke gcj-dbtool.
$(db_name): gcj-dbtool$(EXEEXT)
## In case it exists already.
@rm -f $(db_name)
## 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.
./gcj-dbtool -n $(db_name) || touch $(db_name)
--
Summary: libjava build doesn't stop when there is a fatal error
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: java
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: hjl at lucon dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25847
