summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMartin Pool <mbp@samba.org>2002-03-19 05:52:34 +0000
committerMartin Pool <mbp@samba.org>2002-03-19 05:52:34 +0000
commit24448f741fdd0d77b5a4aa3d3b0201ded4f5518f (patch)
tree8a87f599fba2b0935943dd4a319cbe35e29778bc
parent76533c52dcdda2af52c892cb2b13206e7070c0a6 (diff)
downloadrsync-24448f741fdd0d77b5a4aa3d3b0201ded4f5518f.tar.gz
rsync-24448f741fdd0d77b5a4aa3d3b0201ded4f5518f.tar.bz2
rsync-24448f741fdd0d77b5a4aa3d3b0201ded4f5518f.zip
Clean up sgml.
Add note about building with gcc.
-rw-r--r--doc/rsync.sgml19
1 files changed, 18 insertions, 1 deletions
diff --git a/doc/rsync.sgml b/doc/rsync.sgml
index 06719fab..09f826e6 100644
--- a/doc/rsync.sgml
+++ b/doc/rsync.sgml
@@ -253,10 +253,27 @@ running rsync giving the network directory.
</qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ Why is rsync so much bigger when I build it with
+ <command>gcc</command>?
+ </para>
+ </question>
+ <answer>
+ <para>
+ On gcc, rsync builds by default with debug symbols
+ included. If you strip both executables, they should end
+ up about the same size. (Use <command>make
+ install-strip</command>.)
+ </para>
+ </answer>
+ </qandaentry>
+
<qandaentry>
<question>
- Is rsync useful for a single large file like an ISO image?
+ <para>Is rsync useful for a single large file like an ISO image?</para>
</question>
<answer>
<para>