Browse Source

Update email address, gzip 1.3 location, and Sparc GCC bugs.

Paul Eggert 24 years ago
parent
commit
ffcddc2e16
1 changed files with 19 additions and 18 deletions
  1. 19 18
      README

+ 19 - 18
README

@@ -54,11 +54,11 @@ to the report address; rather take special arrangement with the maintainer.
 Your feedback will help us to make a better and more portable package.
 Your feedback will help us to make a better and more portable package.
 Consider documentation errors as bugs, and report them as such.  If you
 Consider documentation errors as bugs, and report them as such.  If you
 develop anything pertaining to `tar' or have suggestions, let us know
 develop anything pertaining to `tar' or have suggestions, let us know
-and share your findings by writing at `tar-forum@iro.umontreal.ca'.
+and share your findings by writing to <bug-tar@gnu.org>.
 
 
-.--------------------.
-| Installation hints |
-`--------------------'
+
+Installation hints
+------------------
 
 
 Here are a few hints which might help installing `tar' on some systems.
 Here are a few hints which might help installing `tar' on some systems.
 
 
@@ -78,16 +78,17 @@ If you see the following symptoms:
    tar: Child returned status 2
    tar: Child returned status 2
 
 
 then you have encountered a gzip incompatibility that should be fixed
 then you have encountered a gzip incompatibility that should be fixed
-in gzip 1.3, which is not yet available as of this writing.  You can
-work around the incompatibility by using a shell command like
-`gzip -d <file.tar.gz | tar -xzf -'.
+in gzip test version 1.3, which as of this writing is available at
+<ftp://alpha.gnu.org/gnu/gzip/>.  You can work around the
+incompatibility by using a shell command like
+ `gzip -d <file.tar.gz | tar -xzf -'.
 
 
 * Solaris issues.
 * Solaris issues.
 
 
-If you are compiling with GCC, you may need to upgrade GCC to 2.95.2
-or later before compiling GNU tar, as GNU tar exercises many features
-that can cause problems with older GCC versions, mostly having to do
-with mutations to Solaris system include files.
+GNU tar exercises many features that can cause problems with older GCC
+versions.  In particular, GCC 2.8.1 (sparc, -O1 or -O2) is known to
+miscompile GNU tar.  No compiler-related problems have been reported
+when using GCC 2.95.2 or later.
 
 
 Recent versions of Solaris tar sport a new -E option to generate
 Recent versions of Solaris tar sport a new -E option to generate
 extended headers in an undocumented format.  GNU tar does not
 extended headers in an undocumented format.  GNU tar does not
@@ -106,7 +107,7 @@ to a value from the table below, before configuration (see `INSTALL').
 	Platform	Compiler	LDFLAGS
 	Platform	Compiler	LDFLAGS
 
 
 	(any)		Gnu C		-static
 	(any)		Gnu C		-static
-	AIX		(vendor)	"-bnso -bI:/lib/syscalls.exp"
+	AIX		(vendor)	-bnso -bI:/lib/syscalls.exp
 	HPUX		(vendor)	-Wl,-a,archive
 	HPUX		(vendor)	-Wl,-a,archive
 	IRIX		(vendor)	-non_shared
 	IRIX		(vendor)	-non_shared
 	OSF		(vendor)	-non_shared
 	OSF		(vendor)	-non_shared
@@ -114,12 +115,12 @@ to a value from the table below, before configuration (see `INSTALL').
 	Solaris		(vendor)	-Bstatic
 	Solaris		(vendor)	-Bstatic
 	SunOS		(vendor)	-Bstatic
 	SunOS		(vendor)	-Bstatic
 
 
-* Failed `incremen.sh'.
+* Failed test `incremen.sh'.
 
 
 In an NFS environment, lack of synchronization between machine clocks
 In an NFS environment, lack of synchronization between machine clocks
 might create difficulties to any tool comparing dates and file time stamps,
 might create difficulties to any tool comparing dates and file time stamps,
-like `tar' in incremental dumps.  This has been a recurrent problem in
-GNU Makefiles for the last few years.  We would like a general solution.
+like `tar' in incremental dumps.  This has been a recurrent problem with
+GNU Make for the last few years.  We would like a general solution.
 
 
 * BSD compatibility matters.
 * BSD compatibility matters.
 
 
@@ -134,9 +135,9 @@ This file is not a real file, but some kind of uncompressed view of
 the real compressed swap file; there is no reason to back it up, so
 the real compressed swap file; there is no reason to back it up, so
 the simplest workaround is to avoid tarring this file.
 the simplest workaround is to avoid tarring this file.
 
 
-.------------------.
-| Special topics.  |
-`------------------'
+
+Special topics
+--------------
 
 
 Here are a few special matters about GNU `tar', not related to build
 Here are a few special matters about GNU `tar', not related to build
 matters.  See previous section for such.
 matters.  See previous section for such.