This is a list of problems (and some apparent problems which don't really mean anything is wrong) that show up during installation of GNU CC.
CC
can interfere with the functioning of make
.
fixincludes
if the
System V file system doesn't support symbolic links. These problems
result in a failure to fix the declaration of size_t
in
`sys/types.h'. If you find that size_t
is a signed type and
that type mismatches occur, this could be the cause.
The solution is not to use such a directory for building GNU CC.
gcc
driver program looked for
as
and ld
in various places; for example, in files
beginning with `/usr/local/lib/gcc-'. GNU CC version 2 looks for
them in the directory
`/usr/local/lib/gcc-lib/target/version'.
Thus, to use a version of as
or ld
that is not the system
default, for example gas
or GNU ld
, you must put them in
that directory (or make links to them from that directory).
make
. These failures, which
are often due to files that were not found, are expected, and can safely
be ignored.
make
recompiles parts of the compiler when installing
the compiler. In one case, this was traced down to a bug in
make
. Either ignore the problem or switch to GNU Make.
enquire
, which is part of building
GNU CC. The fix is to get rid of the file real-ld
which purify
installs--so that GNU CC won't try to use it.
__GNU_LIBRARY__
conditional
around line 31 to `#if 1'.
enquire
hangs due to a hardware problem in the motherboard--it
reports floating point exceptions to the kernel incorrectly. You can
install GNU CC except for `float.h' by patching out the command to
run enquire
. You may also be able to fix the problem for real by
getting a replacement motherboard. This problem was observed in
Revision E of the Micronics motherboard, and is fixed in Revision F.
It has also been observed in the MYLEX MXA-33 motherboard.
If you encounter this problem, you may also want to consider removing
the FPU from the socket during the compilation. Alternatively, if you
are running SCO Unix, you can reboot and force the FPU to be ignored.
To do this, type `hd(40)unix auto ignorefpu'.
ln /etc/emulator.rel1 /etc/emulatorand then reboot the system. (The default emulator file remains present under the name `emulator.dflt'.) Try using `/etc/emulator.att', if you have such a problem on the SCO system. Another system which has this problem is Esix. We don't know whether it has an alternate emulator that works. On NetBSD 0.8, a similar problem manifests itself as these error messages:
enquire.c: In function `fprop': enquire.c:2328: floating overflow
genflags
or genoutput
while building GNU CC. This is said to
be due to a bug in sh
. You can probably get around it by running
genflags
or genoutput
manually and then retrying the
make
.
pkginfo
command. To add an optional package, use the
pkgadd
command. For further details, see the Solaris
documentation.
For Solaris 2.0 and 2.1, GNU CC needs six packages: `SUNWarc',
`SUNWbtool', `SUNWesu', `SUNWhea', `SUNWlibm', and
`SUNWtoo'.
For Solaris 2.2, GNU CC needs an additional seventh package: `SUNWsprot'.
PATH
.
gcc
compiler fills a branch delay slot with a
floating point instruction, such as add.d
.
fixincludes
. This causes
problems in building GNU CC. Once GNU CC is installed, the problems go
away.
To work around this problem, when making the stage 1 compiler, specify
this option to Make:
GCC_FOR_TARGET="./xgcc -B./ -I./include"When making stage 2 and stage 3, specify this option:
CFLAGS="-g -I./include"
alloca
against shared
libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug
in the linker, that is supposed to be fixed in future revisions.
To protect against this, GNU CC passes `-non_shared' to the
linker unless you pass an explicit `-shared' or
`-call_shared' switch.
ld fatal: failed to write symbol name something in strings table for file whateverThis probably indicates that the disk is full or your ULIMIT won't allow the file to be as large as it needs to be. This problem can also result because the kernel parameter
MAXUMEM
is too small. If so, you must regenerate the kernel and make the value
much larger. The default value is reported to be 1024; a value of 32768
is said to work. Smaller values may also work.
/usr/local/lib/bison.simple: In function `yyparse': /usr/local/lib/bison.simple:625: virtual memory exhaustedthat too indicates a problem with disk space, ULIMIT, or
MAXUMEM
.
MAXUMEM = 4096
_floatdisf cc1: warning: `-g' option not supported on this version of GCC cc1: warning: `-g1' option not supported on this version of GCC ./xgcc: Internal compiler error: program as got fatal signal 11`archive/cph/hpux-8.0-assembler', a patched version of the assembler, is available by anonymous ftp from
altdorf.ai.mit.edu
.
If you have HP software support,
the patch can also be obtained directly from HP, as described in the
following note:
This is the patched assembler, to patch SR#1653-010439, where the assembler aborts on floating point constants. The bug is not really in the assembler, but in the shared library version of the function "cvtnum(3c)". The bug on "cvtnum(3c)" is SR#4701-078451. Anyway, the attached assembler uses the archive library version of "cvtnum(3c)" and thus does not exhibit the bug.This patch is also known as PHCO_4484.
fixproto
shell script triggers a bug in the system shell.
If you encounter this problem, upgrade your operating system or
use BASH (the GNU shell) to run fixproto
.
muldi3
in file `libgcc2.c'.
You may be able to succeed by getting GNU CC version 1, installing it,
and using it to compile GNU CC version 2. The bug in the Pyramid C
compiler does not seem to affect GNU CC version 1.
va_arg
when you build GNU CC.
If this happens, then you need to link most programs with the library
`iclib.a'. You must also modify `stdio.h' as follows: before
the lines
#if defined(__i860__) && !defined(_VA_LIST) #include <va_list.h>insert the line
#if __PGC__and after the lines
extern int vprintf(const char *, va_list ); extern int vsprintf(char *, const char *, va_list ); #endifinsert the line
#endif /* __PGC__ */These problems don't exist in operating system version 1.1.
./fixproto: sh internal 1K buffer overflowTo fix this, change the first line of the fixproto script to look like:
#!/bin/ksh