Subject: Postscript problems with IRIX
From: Bob Monaghan (bob@sbst.com)
Date: Tue Dec 14 1999 - 19:51:07 CST
Interestingly, when I was compiling abiword 0.77, these warnings popped
up.
I am willing to bet that these certainly have something to do with the
lack
of printing on the IRIX version..
The first error I know something about. IRIX is not BSD compatible by
default.
IRIX prefers the use of POSIX calls vs. BSD calls. ie: Posix "sigaction"
instead
of BSD "signal". This info was found on an SGI website page about
compiling "freeware".
I'll try to hunt it down. Whether or not this is the cause of the
printing bug, I don't know.. :)
I'll be doing some research to see what else I can learn to help fix
these probs..
These are the warning that were printed...
xap_UnixPSGenerate.cpp: In method `void
ps_Generate::doProtectFromPipe()':
xap_UnixPSGenerate.cpp:237: warning: ANSI C++ prohibits conversion from
`(int)' to `(...)'
xap_UnixPSGenerate.cpp: In method `void
ps_Generate::undoProtectFromPipe()':
xap_UnixPSGenerate.cpp:242: warning: ANSI C++ prohibits conversion from
`(int)' to `(...)'
xap_UnixPSGenerate.cpp: In function `static void
ps_Generate::pipeSignalHandler(int)':
xap_UnixPSGenerate.cpp:252: warning: ANSI C++ prohibits conversion from
`(int)' to `(...)'
xap_UnixPSParseAFM.c:
xap_UnixPSImage.cpp:
xap_UnixPSGraphics.cpp:
xap_UnixPSGraphics.cpp: In method `void
PS_Graphics::_emit_IncludeResource()':
xap_UnixPSGraphics.cpp:631: warning: comparison is always 1 due to
limited range of data type
bob..
-- Bob Monaghan - Systems Manager Santa Barbara Studios, Inc. Suite 300, 201 N. Calle Cesar Chavez Santa Barbara, CA 93103 U.S.A.
This archive was generated by hypermail 2b25 : Tue Dec 14 1999 - 19:54:12 CST