--- a/ChangeLog	Sat Dec 14 04:39:00 1996 +0000
+++ b/ChangeLog	Sat Dec 14 15:47:16 1996 +0000
@@ -1,3 +1,8 @@
+Sat Dec 14 09:46:50 1996  John W. Eaton  <jwe@bevo.che.wisc.edu>
+
+	* README.Linux: New file.
+	* octMakefile.in: Distribute it.
+
 Fri Dec 13 22:37:49 1996  John W. Eaton  <jwe@bevo.che.wisc.edu>
 
 	* configure.in (TERMLIBS): Look for termcap and terminfo after

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/README.Linux	Sat Dec 14 15:47:16 1996 +0000
@@ -0,0 +1,46 @@
+Since July 1996, most work on Octave has been done using a
+Linux/GNU system.
+
+If you have trouble compiling or running Octave on a Linux/GNU system,
+it is very likely that the problem is with your system, or your
+installation of the compiler and libraries, and not with Octave
+itself.
+
+For example, if you can compile Octave, but it crashes with a
+segmentation fault right away, you probably have incompatible versions
+of libc and libg++ installed, or you have a version of the dynamic
+loader, ld.so, that is incompatible with your versions of the
+libraries, or both.
+
+On my development system, I am using the following software:
+
+  * Linux kernel 2.0.6
+  * gcc/g++ 2.7.2
+  * libg++/libstdc++ 2.7.1.0
+  * libm 5.0.5
+  * libc 5.2.18
+  * libncurses 3.0
+  * ld.so 1.7.14
+
+I know from experience that the versions listed above seem to work
+well together, but they may not work for you, because if you have a
+newer version of the kernel, you may need a newer version of the C
+library.  Other than that, I don't have time to keep up with all the
+various library versions (life is much too short for that), nor do I
+know which combinations are supposed to work together.  That sort of
+information should be clearly stated in the release notes for the
+libraries.  If it is not, please ask the maintainers of the libraries
+to clarify the documentation.
+
+If you can't compile Octave, you should first check to see that your
+compiler and header files are properly installed.  Do you have
+multiple versions of the g++ include files on your system?  Are you
+sure that your copy of g++ is finding the right set (compiling a short
+program with g++ -v will tell you the search path)?
+
+John W. Eaton
+jwe@bevo.che.wisc.edu
+University of Wisconsin-Madison
+Department of Chemical Engineering
+
+Sat Dec 14 09:44:05 1996

--- a/octMakefile.in	Sat Dec 14 04:39:00 1996 +0000
+++ b/octMakefile.in	Sat Dec 14 15:47:16 1996 +0000
@@ -24,10 +24,10 @@
 
 DISTFILES = $(CONF_DISTFILES) \
 	BUGS COPYING INSTALL INSTALL.OCTAVE NEWS NEWS.[0-9] PROJECTS \
-	README README.NLP README.Windows ROADMAP SENDING-PATCHES \
-	THANKS move-if-change octave.sh octave-bug.in doinstall.sh \
-	mkinstalldirs mkoctfile.in texi2dvi INFO.PATCH MAKEINFO.PATCH \
-	ChangeLog ChangeLog.[0-9]
+	README README.Linux README.NLP README.Windows ROADMAP \
+	SENDING-PATCHES THANKS move-if-change octave.sh octave-bug.in \
+	doinstall.sh mkinstalldirs mkoctfile.in texi2dvi INFO.PATCH \
+	MAKEINFO.PATCH ChangeLog ChangeLog.[0-9]
 
 # Complete directory trees to distribute.
 DISTDIRS = emacs glob kpathsea make # plplot
@@ -41,7 +41,7 @@
 
 # Subdirectories in which to run `make dist'.
 DISTSUBDIRS = libcruft liboctave info readline dlfcn src scripts \
-	test doc examples 
+	test doc examples
 
 BINDISTFILES = COPYING ChangeLog NEWS README THANKS INSTALL.OCTAVE \
 	BUGS PROJECTS octave-bug octave.sh doinstall.sh \