> Dave,
>  take a look at this ... 
> 
> It's been rumoured that Keith Refson said:
> > 
> > I have succeeded in compiling 1.3.7 on a Sun Sparc solaris 8 system.
> > However on startup it puts up one small window with the ominous title
> > "gnome segv" and a yellow-bar-on-red-crcle logo.
> > 
> > Starting under gdb reveals:
> > 
> > Program received signal SIGBUS, Bus error.
> > 0x6f0f4 in md5_process_block (buffer=0xffbed6da, len=64, ctx=0xc86ec)
> >     at guid/md5.c:323
> > 323           OP (A, B, C, D,  7, 0xd76aa478);
> > (gdb)
> > 
> > 
> > #0  0x6f0f4 in md5_process_block (buffer=0xffbed6da, len=64, ctx=0xc86ec)
> >     at guid/md5.c:323
> > #1  0x6f050 in md5_process_bytes (buffer=0xffbed69a, len=70, ctx=0xc86ec)
> >     at guid/md5.c:237
> > #2  0x6e700 in init_from_dir (dirname=0xa7eb8 "/proc", max_files=26)
> >     at guid/guid.c:186
> 
> I assume this is because solaris doesn't use /proc the same as linux,
> and/or needs root permissions. etc.

Keith and I have been working on this. The problem is not
permissions, it's a memory alignment issue, the sparc requires
32-bit aligned integers, and the buffer being passed into the
md5 routine is not aligned correctly.

dave

Reply via email to