On 8/2/06, Erwin Rol mailinglists@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
On Wed, 2006-12-27 at 12:12 -0500, Deji Akingunola wrote:
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.
java-1.4.2-gcj-compat
Thanks,
AG