classmap.db build fail does not fail libjava build

Richard Guenther rguenther@suse.de
Wed Sep 5 14:35:00 GMT 2007


On Wed, 5 Sep 2007, Andrew Haley wrote:

> Richard Guenther writes:
>  > 
>  > because of:
>  > 
>  > ## 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)
>  > 
>  > I think this is a bad thing as I am seeing:
>  > 
>  > make[2]: Leaving directory 
>  > `/abuild/rguenther/obj/x86_64-unknown-linux-gnu/libjava'
>  > ./gcj-dbtool -n classmap.db || touch classmap.db
>  > Exception during runtime initialization
>  > /bin/sh: line 1: 16812 Aborted                 ./gcj-dbtool -n classmap.db
>  > 
>  > and lots of libjava failures that are similar.
> 
> Sure, but that's because your compiler patch breaks Java.  There's
> nothing wrong with the libjava Makefile.

Sure - I would have prefered if the libjava build would have failed
here instead of forcing me through all the testsuites ;)

Richard.



More information about the Gcc-patches mailing list