diff --git a/ChangeLog b/ChangeLog
index e1a75583..f3d1f078 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -2,6 +2,9 @@ CVS code -
- configure.in:
- Fix for _use_keypad check breaking slang support (Christian
Weisgerber).
+- faq.html:
+ - Added some info on making the binary smaller with the configure
+ script.
- files.c:
real_dir_from_tilde()
- Oops, fix case where buf ="~", silly crash (bug discovered by
diff --git a/faq.html b/faq.html
index ca7f14b1..574bb276 100644
--- a/faq.html
+++ b/faq.html
@@ -48,7 +48,9 @@ THE HECK DO I DO NOW?
3.4. I get errors about 'bindtextdomain',
'gettext' and/or 'gettextdomain'. What can I do about it?
3.5. Nano should automatically
-run strip on the binary when installing it!
+run strip on the binary when installing it!
+
3.6. How can I make the
+executable smaller? This is too bloated!
(again, where x.y.z is the version number in question). Then you need to run configure with any options you might want (if any).
The average case is this: -
./configure +
cd nano-x.y.z/
+
./configure
make
make install (as root, of course)
@@ -340,8 +343,31 @@ run strip on the binary when installing it!
make install-strip. The default make install does not, and will
not, run strip automatically.
-
Actually, there are several parts of the +editor that can be disabled. You can pass arguments to the +configure script that disable certain features. Here's a brief +list: ++--disable-tabcomp Disables tab completion code for a smaller binary +--disable-justify Disable justify/unjustify function +--disable-speller Disables spell checker function +--disable-help Disables help function (^G) +--disable-browser Disables mini file browser +
+There's also the --enable-tiny option which disabled everything +above, as well as some larger chunks of the program (like the marker code +that you use Control-^ to select with). Also, if you know you aren't +going to be using other languages you can use --disable-nls to +disable internationalization and save a few K to a few dozen K depending +on if you have locale support on your system. And finally there's always +good old strip to strip all debugging code and code that exists in +libraries on your system. +