Node:Platform specific UNIX notes, Next:Redistributable files UNIX, Previous:UNIX foreign language interface, Up:Release notes and installation guide for UNIX

Platform Specific Notes

This section contains some installation notes which are platform specific under UNIX.

• Solaris SPARC 64bit: You cannot install (or build) the 64 bit version of SICStus using gcc. You need to use the Sun Workshop/Forte compiler. InstallSICStus will try to find it during installation but if that fails, you can set the environment variable CC to e.g. /opt/SUNWspro/bin/cc before invoking InstallSICStus.
• Solaris SPARC 64bit: The following libraries are not supported: library(bdb), library(tcltk).
• Solaris SPARC and x86 The memory management bottom layer is based on malloc()/MM_USE_MALLOC instead of the usual sbrk()/MM_USE_SBRK. The latter did not work reliably. This is as if sicstus -m was always used.
• MacOS X: Installing and using library(tcltk) requires Tk which is not installed on MacOS X by default (see Tcl/Tk Notes).
• MacOS X: An executable built with spld will only work if there is a properly configured subdirectory sp-3.9.1 in the same directory as the executable; see UNIX Runtime Systems on Target Machines.

  Alternatively, the option --wrapper can be passed to spld. In this case a wrapper script is created that will set up various environment variables and invoke the real executable.

• MacOS X: It is not possible to prelink dynamic foreign resources into a dynamically linked Prolog executable. That is, except for data resources, spld --resources ... does not work, whereas spld --static --resources ... will. This is no great loss; pre-linking dynamic foreign resources is pointless, at best.
• MacOS X: When using third-party products like Tcl/Tk or BDB, you may need to set-up DYLD_LIBRARY_PATH so that the MacOS X dynamic linker can find them. When using the SICStus development executable (sicstus), a wrapper script does this automatically.
• MacOS X: Sometimes, the default limit on the process's data-segment is unreasonably small, which may lead to unexpected memory allocation failures. To check this limit, do
  

  tcsh> limit data
  datasize 	6144 kbytes
  bash> ulimit -d
  6144
  

  This indicates that the maximum size of the data-segment is only 6 Mb. To remove the limit, do
  

  tcsh> limit data unlimited
  datasize 	unlimited
  bash> ulimit -d unlimited
  bash> ulimit -d
  unlimited
  

  Please note: limit (ulimit) is a shell built-in in csh/tcsh (sh/bash). It may have a different name in other shells.
• IRIX spld --moveable implies --wrapper. This is due to limitations in the IRIX run-time loader.
• IRIX Pre-linked dynamic resources will not be found at run-time if the executable was built with spld --moveable. This should not be a problem; pre-linked dynamic resources are not recommended anyway.
• AIX Applications that embed the SICStus run-time need to use the Large Address-Space Model. This is done automatically by spld. If you do not use spld, you need to set this option yourself. This is achieved by linking the executable using the -bmaxdata option. An alternative may be to set the environment variable LDR_CNTRL appropriately. See the documentation for the AIX command ld.