summaryrefslogtreecommitdiffstats
path: root/doc/applying-patches.txt
diff options
context:
space:
mode:
authorThomas Roessler <roessler@does-not-exist.org>1998-10-08 12:45:13 +0000
committerThomas Roessler <roessler@does-not-exist.org>1998-10-08 12:45:13 +0000
commita2a26ea81b9ef1a3987f5473386c80d4e57c69c1 (patch)
tree550d93d330e9f8143f051e988246e97ec285709a /doc/applying-patches.txt
parent85da402e0a6e4fd5a29e0a816fb7d105e63e533e (diff)
Some more documentation; install the html version of the manual if
it's there.
Diffstat (limited to 'doc/applying-patches.txt')
-rw-r--r--doc/applying-patches.txt24
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/applying-patches.txt b/doc/applying-patches.txt
new file mode 100644
index 00000000..7c9e3b5b
--- /dev/null
+++ b/doc/applying-patches.txt
@@ -0,0 +1,24 @@
+Subject: Applying patches
+From: Thomas Roessler <roessler@guug.de>
+Date: Thu, 8 Oct 1998 14:32:53 +0200
+
+When applying patches to mutt, you may encounter strange error
+messages spit out by programs like aclocal, autoconf, automake.
+This will happen if your machine has a partial build environment
+(see devel-notes.txt for a description of what's needed for mutt
+development): Mutt has detected changes to some of the "meta source
+files" like configure.in and tries to rebuild other files such as
+aclocal.m4 or Makefile.in based on these changes; this will fail if
+your build environment is not complete.
+
+If you encounter this kind of problem, touching the following files
+after applying patches may help:
+
+ Makefile.in
+ config.h.in
+ configure
+ aclocal.m4
+
+After doing so, simply type "make"; the dependencies should take
+care of the necessary other re-building (this may quite well include
+a re-running of ./configure).