755 |
|
|
756 |
Iris 4D (mips-sgi-irix[456].*) |
Iris 4D (mips-sgi-irix[456].*) |
757 |
|
|
758 |
|
Emacs 21.3 is reported to work on IRIX 6.5.x. |
759 |
|
|
760 |
You can build a 64-bit executable (with larger maximum buffer size) |
You can build a 64-bit executable (with larger maximum buffer size) |
761 |
on Irix 6.5 by specifying the 64-bit ABI using the `-64' compiler |
on Irix 6.5 by specifying the 64-bit ABI using the `-64' compiler |
762 |
flag or otherwise (see cc(1)). This may work on earlier Irix 6 |
flag or otherwise (see cc(1)). This may work on earlier Irix 6 |
763 |
systems if you edit src/s/irix6-0.h following irix6-5.h. |
systems if you edit src/s/irix6-0.h following irix6-5.h. |
764 |
|
|
|
Building Emacs 21.1 and 21.2 on versions of Irix before 6.5.10, |
|
|
especially when Emacs is built with GCC, was reported to have subtle |
|
|
problems such as being unable to print to stdout under the -batch |
|
|
command-line option. Building with the native compiler or upgrading |
|
|
the OS to a newer version solves these problems. There's evidence |
|
|
that these problems are actually related to the runtime libraries |
|
|
(before IRIX 6.5.10, the IRIX runtimes were based on the MIPSpro 7.2 |
|
|
compilers), so installing patches for the runtime from |
|
|
http://www.sgi.com/support/patch_intro.html could solve the problem |
|
|
even without upgrading the OS. The dump process is the crucial |
|
|
step that needs the upgraded runtime, so a workaround is to dump |
|
|
Emacs on a machine with a newer OS, then copy the binary to the |
|
|
older OS. |
|
|
|
|
765 |
If compiling with GCC on Irix 6 yields an error "conflicting types |
If compiling with GCC on Irix 6 yields an error "conflicting types |
766 |
for `initstate'", install GCC 2.95 or a newer version, and this |
for `initstate'", install GCC 2.95 or a newer version, and this |
767 |
problem should go away. It is possible that this problem results |
problem should go away. It is possible that this problem results |
769 |
could also try reinstalling the same version of GCC, and telling us |
could also try reinstalling the same version of GCC, and telling us |
770 |
whether that fixes the problem. |
whether that fixes the problem. |
771 |
|
|
|
The 19.26 pretest was reported to work on IRIX 4.0.5 and 5.2. |
|
|
19.23 was reported to work on IRIX 5.2, but you may need to install |
|
|
the "compiler_dev.hdr.internal" subsystem in order to compile unexelfsgi.c. |
|
|
19.22 was known to work on all Silicon Graphics machines running |
|
|
IRIX 4.0.5 or IRIX 5.1. |
|
|
|
|
|
Compiling with -O using IRIX compilers prior to 3.10.1 may not work. |
|
|
Don't use -O or use GCC instead. |
|
|
|
|
|
Most IRIX 3.3 systems do not have an ANSI C compiler, but a few do. |
|
|
Compile Emacs 18 with the -cckr switch on these machines. |
|
|
|
|
|
There is a bug in IRIX 3.3 that can sometimes leave ptys owned by root |
|
|
with a permission of 622. This causes malfunctions in use of |
|
|
subprocesses of Emacs. Irix versions 4.0 and later with GNU Emacs |
|
|
versions 18.59 and later fix this bug. |
|
|
|
|
772 |
Masscomp (m68k-masscomp-rtu) |
Masscomp (m68k-masscomp-rtu) |
773 |
|
|
774 |
18.36 worked on a 5500DP running RTU v3.1a and compiler version 3.2 |
18.36 worked on a 5500DP running RTU v3.1a and compiler version 3.2 |