Troubleshooting
This section lists some of the errors you may encounter building the SSCLI, and the corresponding solutions:
- "C compiler cannot create executables"
You will encounter this error on Unix systems where the C compiler is not installed or not configured properly. On Mac OS X, you will need the Developer Tools (see "Mac OS X Prerequisites,” earlier in this appendix). Under FreeBSD, you should have selected the Developer install when you installed the operating system (see "FreeBSD Prerequisites,” earlier in this appendix).
- “The type or namespace name ‘SR’ could not be found”
This indicates that Perl is not installed. For Windows, you can get Perl from http://www.activestate.com. Mac OS X includes Perl, and it will be installed on FreeBSD if you selected the Developer install during installation.
- "conflicting types for ‘PAL_vfprintf’"
You’ll get this error on Mac OS X if you’re using the gcc2 compiler instead of gcc3. gcc3 is the default on Mac OS X 10.2 (Jaguar). If you’ve changed your C compiler by executing the
gcc_select 2command, you must issue the commandsudo gcc_select 3to change it back to the default. To remove any cruft that may have accumulated while you were using the wrong compiler, run the command./buildall -cfrom the root level of yourssclidirectory tree to rebuild everything from scratch.- "‘mc.exe’ is not recognized as an internal or external command"
You’ll get this error on Windows if Visual Studio .NET is not installed. The current release of the ...