🚀 go-pugleaf

I have tried to install gcc 2.2.2 on a CDC machine running EP/IX 1.4.3
This is a mipsbox with some modifications to the O.S. Its a sysv-bsd
hybrid.

I used mips-sysv as the target for the configure command.

All seems to work well execpt for the following problems:

When doing the "make install-fixincludes" I messages like the ones below:
(The ones I include here for reference are all those tried to treat
string.h)

  ...

  Fixing ./bsd43/string.h
  Deleting /bfu/ltst/lib/gcc-lib/mips-sysv3/2.2.2/include/./bsd43/string.h; no f

  ...

  Fixing ./bsd43/string.h
  Can't copy ./bsd43/string.h
  chmod: WARNING: can't access /bfu/ltst/lib/gcc-lib/mips-sysv3/2.2.2/include/./
  ./fixincludes: /bfu/ltst/lib/gcc-lib/mips-sysv3/2.2.2/include/./bsd43/des/sysv
  mv: /bfu/ltst/lib/gcc-lib/mips-sysv3/2.2.2/include/./bsd43/des/sysv/./bsd43/st

  ...

  Fixing ./bsd43/string.h
  Can't copy ./bsd43/string.h
  chmod: WARNING: can't access /bfu/ltst/lib/gcc-lib/mips-sysv3/2.2.2/include/./
  ./fixincludes: /bfu/ltst/lib/gcc-lib/mips-sysv3/2.2.2/include/./bsd43/sysv/./b
  mv: /bfu/ltst/lib/gcc-lib/mips-sysv3/2.2.2/include/./bsd43/sysv/./bsd43/string

  ...

  Fixing ./bsd43/string.h
  Can't copy ./bsd43/string.h
  chmod: WARNING: can't access /bfu/ltst/lib/gcc-lib/mips-sysv3/2.2.2/include/./
  ./fixincludes: /bfu/ltst/lib/gcc-lib/mips-sysv3/2.2.2/include/./posix/sysv/./b
  mv: /bfu/ltst/lib/gcc-lib/mips-sysv3/2.2.2/include/./posix/sysv/./bsd43/string

  ...

Note too that there is no mentioning of fixing ./string.h although that does exi
Which is probably the cause of the following warnings I almost always receive wh
compiling things:

          stage3/gcc -Bstage3/ -c    -g -O     -I. -I. -I./config cp-lex.c
  In file included from cp-lex.c:28:
  /sysv/usr/include/string.h:53: warning: conflicting types for built-in functio
  /sysv/usr/include/string.h:59: warning: conflicting types for built-in functio

Can someone tell me what I should do to repair these or at least give
me an idea where too look.

And now that I'am asking is the following something to worry about?

          ar qc libgcc1.null dummy.o
  ar: Warning:ignoring second definition of __foo defined in archive
  ar: Warning:ignoring second definition of __foo defined in archive
  ar: Warning:ignoring second definition of __foo defined in archive


========================================================================
Antoon Pardon                                    <apardon@is1.vub.ac.be>
Brussels Free University Computing Centre                   02/650.37.16
========================================================================
--
========================================================================
Antoon Pardon                                    <apardon@is1.vub.ac.be>
Brussels Free University Computing Centre                   02/650.37.16
========================================================================