java-1.4.2-gcj-compat postinstall (in mock) fault - [WAS]Re: rawhide report: 20060802 changes

[Deji Akingunola]

On 8/2/06, Erwin Rol <mailinglists at erwinrol.com> wrote:
> This update also caused the following errors on x86_&4;
>
> Running Transaction
>   Updating  : java-1.4.2-gcj-compat        ####################### [ 1/66]
> dirname: missing operand
> Try `dirname --help' for more information.
> mkdir: missing operand
> Try `mkdir --help' for more information.
> /usr/bin/rebuild-gcj-db: line 17: 20713 Segmentation fault      /usr/bin/gcj-dbtool -n $dbLocation 64
> xargs: /usr/bin/gcj-dbtool: terminated by signal 11
> dirname: missing operand
> Try `dirname --help' for more information.
> mkdir: missing operand
> Try `mkdir --help' for more information.
> /usr/bin/rebuild-gcj-db: line 17: 20722 Segmentation fault      /usr/bin/gcj-dbtool -n $dbLocation 64
> xargs: /usr/bin/gcj-dbtool: terminated by signal 11

I'm getting this same segmentation fault in the root log of a mock
build that needs java-1.4.2-gcj-compat. Which package should I filled
this against, glibc or libgcj or java-1.4.2-gcj-compat.

Deji