summaryrefslogtreecommitdiff
path: root/doc/FAQ
diff options
context:
space:
mode:
authorgoodale <goodale@17b73243-c579-4c4c-a9d2-2d5706c11dac>1999-06-24 09:08:38 +0000
committergoodale <goodale@17b73243-c579-4c4c-a9d2-2d5706c11dac>1999-06-24 09:08:38 +0000
commit783c1e783a38360923d31e6aff695fd9114718aa (patch)
treef49ceb17b722155b1defde0864d373229fc1ff95 /doc/FAQ
parent8311d85b42739c0fdead2d4b851986771001e727 (diff)
A FAQ for potentially useful stuff which has no logical place in the
documentation. Tom git-svn-id: http://svn.cactuscode.org/flesh/trunk@569 17b73243-c579-4c4c-a9d2-2d5706c11dac
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ25
1 files changed, 25 insertions, 0 deletions
diff --git a/doc/FAQ b/doc/FAQ
new file mode 100644
index 00000000..b7fa16db
--- /dev/null
+++ b/doc/FAQ
@@ -0,0 +1,25 @@
+# /*@@
+# @file FAQ
+# @date Thu Jun 24 11:06:01 1999
+# @author Tom Goodale
+# @desc
+# Some useful info.
+# @enddesc
+# @version $Header: /mnt/data2/cvs2svn/cvs-repositories/Cactus/doc/FAQ,v 1.1 1999-06-24 09:08:38 goodale Exp $
+# @@*/
+
+
+1) The make system says "Checking status of libXXX.a" and then just sits there. What
+can I do ?
+
+The first thing to do whenever a problem arises from the make system is to run with
+the "SILENT=no" option.
+
+In this case, 'though, first check that the clocks on the machine on which you are
+editing files and the clock on the machine you are compiling on are synchronised. If
+the compilation machine's clock is slow, then the newly made dependency files will
+still be `older' than the file you edited, and the system will loop until this
+situation changes.
+
+
+