This is the README file from the sparc binary distribution of GNAT. To find the latest updates on GNAT release status, including any corrections to procedures described in this file, get the README from NYU that can be retrieved by anonymous ftp from cs.nyu.edu:pub/gnat or by sending mail to gnat-send-readme@cs.nyu.edu. This directory contains the files needed for installing and running GNAT on a sparc running SunOS 4.1. It includes the C compiler also. INSTALLING The quick way to install GNAT is to first run the script 'doconfig' contained in this directory. This will not modify any directories or files in your system, but will create a file called 'doinstall'. This is a script containing the commands to actually do the installation according to the configuration you choose when running 'doconfig'. Run it to do the installation. USE Using GNAT is documented in gnatinfo.txt EXPLANATION of installation Since GCC is normally built from sources, the procedures for installing GCC can (and do) build default directory names into several of the executables at the time of building and installation. At present, it is difficult to provide ways for modifying these directories in this binary distribution. Instead, the binaries here are built with the standard defaults, and directions are provided for working with them even if they cannot be installed in the standard locations. The first 2 options in the configuration script place the binaries in the standard locations; the first on top of an existing GCC installation, and the second option puts files in the standard locations if there is no existing GCC installation. Having the files in the standard locations means that the programs can use their builtin directory names to locate files that are needed. For example, the driver program (gcc) can find the directory containing the compilers and the linker that it calls, and the Ada compiler can find the directories containing the Run Time Library (RTL) sources and objects. If the files in this distribution cannot be installed in the standard locations, then the programs cannot use the built in values, so the user defines environment variables that the programs can use, or specifies directories on the command lines of the various programs. When choosing such an installation, 'doconfig' will also generate a file containing csh commands to set the appropriate environment variables. For further explanation of using environment variables or command line switches, see the documentation in 'gnatinfo.txt'. If you cannot put things in standard directories, you will choose option 3 in the configuration script. After installation, you can permanently work with the installation you have done, or use this binary distribution to build a distribution from the sources -- in which case, you will be able to build in the directories that you choose. The configuration program creates make commands to install the system. The Makefile allows more flexibility than is utilized by 'doconfig'. No more help is provided here -- you must know what you are doing -- except to suggest that a possibly helpful option would be to define 'bindir' separately on the make commmand line. EXAMPLES The examples directory contains simple examples.
1.83 There shouldn't be any problems with the installation. If there are they are probably covered below. The limitations below still apply. 1.82 The -g option with gnat is not functional. There are some problems with the installation which might require some manual intervention. This is mostly just recompiling two files. When you need to recompile these files. cd /usr/local/lib/gcc-lib/m68k-next-ns3/2.6.0/adalib gcc -c /usr/local/adainclude/ada.ads gcc -c /usr/local/adainclude/<some other file>.adb There is also a problem with libgnat.a in the ./m68k-next-ns3/2.6.0/adalib directory. libgnat.a is not being built correctly. Make sure that the fileno.c and fileno.o files are present in this directory then in this directory do rm libgnat.a ar rc libgnat.a fileno.o io-aux.o a-cio.o get_errno.o ranlib libgnat.a This is straight from the Makefile so look there for more details. You do not need to to do this if ar tv libgnat.a shows that all four files were included. This gnat1 probably will not recompile itself nor the next gnat1 release. If you try, I would avoid the -g and the -O for the CFLAGS make variable.
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.
