X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=legacy%2Fdoc%2Fapplying-patches.txt;fp=legacy%2Fdoc%2Fapplying-patches.txt;h=5379ee5c3ede32fad500b07ce424f32853be938f;hp=0000000000000000000000000000000000000000;hb=3ad8157bbbc6b9fae1c3252aad1c07fcccd92004;hpb=2fea7732a573b94a4d5dcf7e641ef067472e9cab

diff --git a/legacy/doc/applying-patches.txt b/legacy/doc/applying-patches.txt
new file mode 100644
index 0000000..5379ee5
--- /dev/null
+++ b/legacy/doc/applying-patches.txt
@@ -0,0 +1,25 @@
+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).
+$Id: applying-patches.txt,v 3.0 2002/01/24 13:35:07 roessler Exp $