Re: libtool man page

2008-09-20 Thread Ralf Wildenhues
* Peter O'Gorman wrote on Sat, Sep 20, 2008 at 05:11:19AM CEST:
 
 This looks ok to me, thank you.

Thanks.  Now that it's a new morning, I see several shortcomings:
* --help-all was not documented at all,
* -h not document in .texi,
* I forgot finish mode in --help-all,
* -Wc,FLAG was not documented in link mode,
* -Wl,FLAG and -XCClinker FLAG were erroneously listed under compile
  mode in the manual, and not included in link mode --help,
* the message as to what to include in a bug report was not output at
  all any more.  So I moved the Report bugs to.. back to where it
  was before, and took care that help2man renders the table of what to
  send in a bug report as table (rather than munged text), and that
  --help-all moves this bit to the very end.

Should all be fixed with this patch, on top of the other two.

Also, I decided to caution and call the @direntry libtool-invocation.
Hope that's ok with you.

The full patch, including ChangeLog entry, can be found here:
http://article.gmane.org/gmane.comp.gnu.libtool.cvs/2695

Cheers,
Ralf

diff --git a/NEWS b/NEWS
index 44d06fb..9dc14e1 100644
--- a/NEWS
+++ b/NEWS
@@ -5,6 +5,7 @@ New in 2.2.8 2008-??-??: git version 2.2.7a, Libtool team:
 * New features:
 
   - Libtool ships and installs man pages for libtool and libtoolize now.
+  - New libtool command line flag --help-all.
 
 * Bug fixes:
 
diff --git a/doc/libtool.texi b/doc/libtool.texi
index 6e4b034..59f3872 100644
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -18,7 +18,8 @@
 
 @dircategory Individual utilities
 @direntry
-* libtool: (libtool)Invoking libtool.   Running the @code{libtool} 
script.
+* libtool-invocation: (libtool)Invoking libtool.
+Running the @code{libtool} 
script.
 * libtoolize: (libtool)Invoking libtoolize. Adding libtool support.
 @end direntry
 
@@ -1145,10 +1146,16 @@ to determine whether shared or static libraries will be 
built.
 @item --finish
 Same as @option{--mode=finish}.
 
[EMAIL PROTECTED] -h
+Display short help message.
+
 @item --help
 Display a help message and exit.  If @[EMAIL PROTECTED] is
-specified, then detailed help for @var{mode} is
-displayed.
+specified, then detailed help for @var{mode} is displayed.
+
[EMAIL PROTECTED] --help-all
+Display help for the general options as well as detailed help for each
+operation mode, and exit.
 
 @item [EMAIL PROTECTED]
 Use @var{mode} as the operation mode.  When using libtool from the
@@ -1166,14 +1173,14 @@ Compile a source file into a libtool object.
 Automatically set the library path so that another program can use
 uninstalled libtool-generated programs or libraries.
 
[EMAIL PROTECTED] finish
-Complete the installation of libtool libraries on the system.
[EMAIL PROTECTED] link
+Create a library or an executable.
 
 @item install
 Install libraries or executables.
 
[EMAIL PROTECTED] link
-Create a library or an executable.
[EMAIL PROTECTED] finish
+Complete the installation of libtool libraries on the system.
 
 @item uninstall
 Delete installed libraries or executables.
@@ -1294,14 +1301,7 @@ linking.
 
 @item -Wc,@var{flag}
 @itemx -Xcompiler @var{flag}
-Pass a linker specific flag directly to the compiler.
-
[EMAIL PROTECTED] -Wl,@var{flag}
[EMAIL PROTECTED] -Xlinker @var{flag}
-Pass a linker specific flag directly to the linker.
-
[EMAIL PROTECTED] -XCClinker @var{flag}
-Pass a link specific flag to the compiler driver (@var{CC}) during linking.
+Pass a flag directly to the compiler.
 @end table
 
 @node Link mode
@@ -1470,12 +1470,16 @@ no need to append @var{libname} to the list of 
dependency libraries of
 @var{output-file}, because linking against @var{output-file} already
 supplies the same interface (@pxref{Linking with dlopened modules}).
 
[EMAIL PROTECTED] -Wc,@var{flag}
[EMAIL PROTECTED] -Xcompiler @var{flag}
+Pass a linker-specific flag directly to the compiler.
+
 @item -Wl,@var{flag}
 @itemx -Xlinker @var{flag}
-Pass a linker specific flag directly to the linker.
+Pass a linker-specific flag directly to the linker.
 
 @item -XCClinker @var{flag}
-Pass a link specific flag to the compiler driver (@var{CC}) during linking.
+Pass a link-specific flag to the compiler driver (@var{CC}) during linking.
 @end table
 
 If the @var{output-file} ends in @samp{.la}, then a libtool library is
diff --git a/libltdl/config/ltmain.m4sh b/libltdl/config/ltmain.m4sh
index 0427acf..ec7de23 100644
--- a/libltdl/config/ltmain.m4sh
+++ b/libltdl/config/ltmain.m4sh
@@ -43,7 +43,7 @@ m4_divert_push([SCRIPT])# @configure_input@
 #   --tag=TAGuse configuration variables from tag TAG
 #   -v, --verboseprint informational messages (default)
 #   --versionprint version information
-#   -h, --help   print short or long help message
+#   -h, --help, --help-all   print short, long, or detailed help message
 #
 # MODE must be one of the following:
 #
@@ -58,8 +58,6 @@ m4_divert_push([SCRIPT])# 

Re: libtool man page

2008-09-20 Thread Peter O'Gorman
Ralf Wildenhues wrote:
 * Peter O'Gorman wrote on Sat, Sep 20, 2008 at 05:11:19AM CEST:
 This looks ok to me, thank you.
 
 Thanks.  Now that it's a new morning, I see several shortcomings:

Haha, for review, I applied your patches, bootstrapped, built and
verified that the resulting manpages worked, I was happy enough with
that. :-)

Peter
-- 
Peter O'Gorman
http://pogma.com