If you're getting a bus error on sparc, then that's probably due to an unaligned memory access. On sparc machines, you can only access memory that is properly aligned. The buildds on ia64 are set with prctl to have this behavior as well, because although (IIRC) the ia64 kernel can fix up unaligned accesses, it is very expensive to do so.
Looking at the ps2pdf shell script, it seems that this is a problem with gs. You might try running the following command by hand to see if you get the same error (maybe under gdb?): gs -dSAFER -dCompatibilityLevel=1.4 -q -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=faq.pdf -dSAFER -dCompatibilityLevel=1.4 -c .setpdfwrite -f faq.ps HTH. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only a typesetting engine: http://crustytoothpaste.ath.cx/~bmc/code/thwack OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
