Browse files

Release 1.11 as of 1992-09-09

  • Loading branch information...
pinard committed Jul 1, 2009
1 parent 49c6ca7 commit 2a7260608b75bbb6083a17da8c173393dbd37b1c
Showing with 11,033 additions and 6,559 deletions.
  1. +222 −132 COPYING
  2. +505 −0 ChangeLog
  3. +111 −0 INSTALL
  4. +0 −316 Makefile
  5. +175 −0
  6. +67 −31 README
  7. +194 −0 alloca.c
  8. +21 −9 backup-specs
  9. +252 −189 buffer.c
  10. +717 −0 configure
  11. +51 −0
  12. +276 −207 create.c
  13. +99 −83 diffarch.c
  14. +447 −370 extract.c
  15. +62 −14 getdate.y
  16. +4 −4 getoldopt.c
  17. +219 −136 getopt.c
  18. +62 −43 getopt.h
  19. +33 −40 getopt1.c
  20. +25 −0 getpagesize.h
  21. +116 −102 gnu.c
  22. +14 −14 level-0
  23. +7 −7 level-1
  24. +143 −55 list.c
  25. +57 −0 makefile.pc
  26. +918 −0 malloc.c
  27. +38 −13 mangle.c
  28. +5 −3 msd_dir.c
  29. +2 −2 msd_dir.h
  30. +3 −5 names.c
  31. +1 −3 open3.h
  32. +53 −0 pathmax.h
  33. +157 −312 port.c
  34. +160 −23 port.h
  35. +4,090 −1,973 regex.c
  36. +434 −204 regex.h
  37. +30 −13 rtape_server.c → rmt.c
  38. +42 −23 rmt.h
  39. +0 −649 rtape_lib.c
  40. +578 −0 rtapelib.c
  41. +294 −206 tar.c
  42. +41 −40 tar.h
  43. +0 −1,289 tar.texinfo
  44. +240 −0 tcexparg.c
  45. +16 −9 testpad.c
  46. +44 −31 update.c
  47. +3 −3 version.c
  48. +5 −6 wildmat.c

Large diffs are not rendered by default.

Oops, something went wrong.
505 ChangeLog

Large diffs are not rendered by default.

Oops, something went wrong.
@@ -0,0 +1,111 @@
+This is a generic INSTALL file for utilities distributions.
+If this package does not come with, e.g., installable documentation or
+data files, please ignore the references to them below.
+To compile this package:
+1. Configure the package for your system. In the directory that this
+file is in, type `./configure'. If you're using `csh' on an old
+version of System V, you might need to type `sh configure' instead to
+prevent `csh' from trying to execute `configure' itself.
+The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation, and
+creates the Makefile(s) (one in each subdirectory of the source
+directory). In some packages it creates a C header file containing
+system-dependent definitions. It also creates a file `config.status'
+that you can run in the future to recreate the current configuration.
+Running `configure' takes a minute or two. While it is running, it
+prints some messages that tell what it is doing. If you don't want to
+see the messages, run `configure' with its standard output redirected
+to `/dev/null'; for example, `./configure >/dev/null'.
+To compile the package in a different directory from the one
+containing the source code, you must use a version of make that
+supports the VPATH variable, such as GNU make. `cd' to the directory
+where you want the object files and executables to go and run
+`configure'. `configure' automatically checks for the source code in
+the directory that `configure' is in and in `..'. If for some reason
+`configure' is not in the source code directory that you are
+configuring, then it will report that it can't find the source code.
+In that case, run `configure' with the option `--srcdir=DIR', where
+DIR is the directory that contains the source code.
+By default, `make install' will install the package's files in
+/usr/local/bin, /usr/local/lib, /usr/local/man, etc. You can specify
+an installation prefix other than /usr/local by giving `configure' the
+option `--prefix=PATH'. Alternately, you can do so by changing the
+`prefix' variable in the Makefile that `configure' creates (the
+Makefile in the top-level directory, if the package contains
+You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If
+you give `configure' the option `--exec_prefix=PATH', the package will
+use PATH as the prefix for installing programs and libraries. Data
+files and documentation will still use the regular prefix. Normally,
+all files are installed using the regular prefix.
+You can tell `configure' to figure out the configuration for your
+system, and record it in `config.status', without actually configuring
+the package (creating `Makefile's and perhaps a configuration header
+file). To do this, give `configure' the `--no-create' option. Later,
+you can run `./config.status' to actually configure the package. This
+option is useful mainly in `Makefile' rules for updating `config.status'
+and `Makefile'. You can also give `config.status' the `--recheck'
+option, which makes it re-run `configure' with the same arguments you
+used before. This is useful if you change `configure'.
+`configure' ignores any other arguments that you give it.
+If your system requires unusual options for compilation or linking
+that `configure' doesn't know about, you can give `configure' initial
+values for some variables by setting them in the environment. In
+Bourne-compatible shells, you can do that on the command line like
+ CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure
+The `make' variables that you might want to override with environment
+variables when running `configure' are:
+(For these variables, any value given in the environment overrides the
+value that `configure' would choose:)
+CC C compiler program.
+ Default is `cc', or `gcc' if `gcc' is in your PATH.
+INSTALL Program to use to install files.
+ Default is `install' if you have it, `cp' otherwise.
+(For these variables, any value given in the environment is added to
+the value that `configure' chooses:)
+DEFS Configuration options, in the form `-Dfoo -Dbar ...'
+LIBS Libraries to link with, in the form `-lfoo -lbar ...'
+If you need to do unusual things to compile the package, we encourage
+you to figure out how `configure' could check whether to do them, and
+mail diffs or instructions to the address given in the README so we
+can include them in the next release.
+2. Type `make' to compile the package. If you want, you can override
+the `make' variables CFLAGS and LDFLAGS like this:
+ make CFLAGS=-O2 LDFLAGS=-s
+3. If the package comes with self-tests and you want to run them,
+type `make check'. If you're not sure whether there are any, try it;
+if `make' responds with something like
+ make: *** No way to make target `check'. Stop.
+then the package does not come with self-tests.
+4. Type `make install' to install programs, data files, and
+5. You can remove the program binaries and object files from the
+source directory by typing `make clean'. To also remove the
+Makefile(s), the header file containing system-dependent definitions
+(if the package uses one), and `config.status' (all the files that
+`configure' created), type `make distclean'.
+The file `' is used as a template to create `configure' by
+a program called `autoconf'. You will only need it if you want to
+regenerate `configure' using a newer version of `autoconf'.
Oops, something went wrong.

0 comments on commit 2a72606

Please sign in to comment.