Supported Platforms. SysInfo™ uses GNU autoconfigure (i.e. A
to configure many system parameters before
compilation. However, this does not mean SysInfo™ will work on any
system. SysInfo™ contains very specific support for specific
platforms as specified in the
Compiling for different OS versions: In general, SysInfo™ will
run on the OS version you compiled it on and later releases. It
will not run on an OS older than the OS version it was compiled on.
There are exceptions to this, including those mentioned below for
Solaris. SysInfo™ defines some (cryptic) rules for each OS which
specify these what OS versions a binary runs on. These rules are
is the name of the OS in lower
is the SunOS/Solaris rule file.
Solaris 7 and later: Starting with Solaris 7 Sun introduced 64-bit Solaris. You will need one SysInfo™ binary for 32-bit systems and one binary for 64-bit systems. Starting with SysInfo™ 6.0.1-GA, you do not need one binary per Solaris version. You need two total binaries - one 32-bit and one 64-bit. Your 32-bit binary will run on 32-bit systems running the same or later version of Solaris. Similiarly your 64-bit binary will run on 64-bit systems running the same or later version of Solaris. (All Ultra machines are 64-bit). You can check which version you are running by executing /usr/bin/isainfo -k -v. If the output says 64-bit you are running a 64-bit kernel.
To build a binary of SysInfo™ for a system running a 64-bit kernel, you must have a compatible compiler. We recommend using Sun ONE Studio (formerly Forte, formerly WorkShop) C compiler on Sun Solaris systems. WorkShop Compiler 6.0.1-GA was the first Sun compiler to support 64-bit systems via the -xarch=v9 option. GCC version 3.2 and later supports 64-bit compiles via the -m64 option. However, MagniComp does not test with this configuration.
By default, a binary that runs on the local system will be
built. You can force a build of a 64-bit binary on a 32-bit system
and vice-versa. To build a 64-bit binary on a 32-bit system, set
the environment variable
sparcv9. To build a 32-bit
binary on a 64-bit system, set KISA to be
sparcv8. i.e. For csh
setenv KISA sparcv9For sh/ksh users:
Makefile:XXX: *.d: No such file or directory During initial
compilation you may see error messages like this. The messages are
perfectly normal and can be safely ignored. They are generated the
first time make is run and indicate that a dependency file does not
exist. It will be automatically generated by make and further such
messages for the indicated file should not appear.