[Raion]

pkgconf, a replacement for, and lighterweight version of, pkg-config is not building with MIPSPro. We've discussed this before:

~/pkgconf-0.9.6 % /usr/local/bin/make -j3
c99 -c -O2 -mips4 -TARG:proc=r10000 -DLIBDIR=\"/usr/share/bsd/lib32\" -DINCLUDEDIR=\"/usr/share/bsd/include\" -DPKG_DEFAULT_PATH=\"/usr/share/bsd/lib32/pkgconfig:/u
sr/share/pkgconfig\" -DSYSTEM_INCLUDEDIR=\"/usr/share/bsd/include\" -DSYSTEM_LIBDIR=\"/usr/share/bsd/lib32\" -Wall  -I. -I/usr/include -I/usr/gnu/include main.c -o
main.o
c99 -c -O2 -mips4 -TARG:proc=r10000 -DLIBDIR=\"/usr/share/bsd/lib32\" -DINCLUDEDIR=\"/usr/share/bsd/include\" -DPKG_DEFAULT_PATH=\"/usr/share/bsd/lib32/pkgconfig:/u
sr/share/pkgconfig\" -DSYSTEM_INCLUDEDIR=\"/usr/share/bsd/include\" -DSYSTEM_LIBDIR=\"/usr/share/bsd/lib32\" -Wall  -I. -I/usr/include -I/usr/gnu/include cache.c -o
cache.o
c99 -c -O2 -mips4 -TARG:proc=r10000 -DLIBDIR=\"/usr/share/bsd/lib32\" -DINCLUDEDIR=\"/usr/share/bsd/include\" -DPKG_DEFAULT_PATH=\"/usr/share/bsd/lib32/pkgconfig:/u
sr/share/pkgconfig\" -DSYSTEM_INCLUDEDIR=\"/usr/share/bsd/include\" -DSYSTEM_LIBDIR=\"/usr/share/bsd/lib32\" -Wall  -I. -I/usr/include -I/usr/gnu/include pkg.c -o p
kg.o
cc-1110 c99: REMARK File = main.c, Line = 627
  The indicated statement is not reachable.

                        break;
                        ^

cc-3943 c99: REMARK File = pkg.c, Line = 474
  declaration hides variable "pkg" (declared at line 463)

                        pkg_t *pkg;
                              ^

Signal: Segmentation fault in Scope Setup phase.
Error: Signal Segmentation fault in phase Scope Setup -- processing aborted
c99 ERROR:  /usr/lib32/cmplrs/fec died due to signal 4
c99 ERROR:  core dumped
Makefile:47: recipe for target 'pkg.o' failed


Clearly, something in pkg.c is killing the compiler. It's post-preprocessor, but during compilation and after line 474

https://github.com/pkgconf/pkgconf/relea...conf-0.9.6

If someone wants to try the same version, though later versions have similar problems with pkg.c when you get over the hump. 

I know this is a C scope issue, but I don't know how to diagnose it further. Does this mean that a C function is just going too deep in scope???