FYI: libtool--devo--1.0--patch-199

[Gary V. Vaughan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Applied to HEAD.
- -- 
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook
_________________________________________________________
This patch notification generated by tlaapply version 0.5
http://tkd.kicks-ass.net/arch/address@hidden/cvs-utils--tla--1.0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Darwin)

iD8DBQFBUsFSFRMICSmD1gYRAk34AJ9Ps1/+i9tD1iJf1+WqnH+B+A7biACfRiKL
9ItuHypyGC0eghvM3GfkDTo=
=S0k2
-----END PGP SIGNATURE-----

* looking for address@hidden/libtool--devo--1.0--patch-198 to compare with
* comparing to address@hidden/libtool--devo--1.0--patch-198
M  ChangeLog
M  doc/libtool.texi
M  m4/libtool.m4

* modified files

Index: Changelog
from  Ralf Wildenhues <address@hidden>

        * m4/libtool.m4 (_LT_CMD_GLOBAL_SYMBOLS): move symcode calculation
        to correct place.
        * doc/libtool.texi (libtool script contents): update description
        of global_symbol_to_cdecl.

04-09-23  Gary V. Vaughan  <address@hidden>
--- orig/doc/libtool.texi
+++ mod/doc/libtool.texi
@@ -5062,16 +5062,15 @@
 $
 @end example
 
-The first column contains the symbol type (used to tell data from code
-on some platforms), but its meaning is system dependent.
+The first column contains the symbol type (used to tell data from code)
+but its meaning is system dependent.
 @end defvar
 
 @defvar global_symbol_to_cdecl
 A pipeline that translates the output of @var{global_symbol_pipe} into
-proper C declarations.  On platforms whose linkers differentiate code
-from data, such as HP/UX, data symbols will be declared as such, and
-code symbols will be declared as functions.  On platforms that don't
-care, everything is assumed to be data.
+proper C declarations.  Since some platforms, such as HP/UX, have
+linkers that differentiate code from data, data symbols are declared
+as data, and code symbols are declared as functions.
 @end defvar
 
 @defvar hardcode_action


--- orig/m4/libtool.m4
+++ mod/m4/libtool.m4
@@ -2720,6 +2720,12 @@
   ;;
 esac
 
+# If we're using GNU nm, then use its standard symbol codes.
+case `$NM -V 2>&1` in
+*GNU* | *'with BFD'*)
+  symcode='[[ABCDGIRSTW]]' ;;
+esac
+
 # Transform an extracted symbol line into a proper C declaration.
 # Some systems (esp. on ia64) link data and code symols differently,
 # so use this general approach.
@@ -2736,12 +2742,6 @@
   ;;
 esac
 
-# If we're using GNU nm, then use its standard symbol codes.
-case `$NM -V 2>&1` in
-*GNU* | *'with BFD'*)
-  symcode='[[ABCDGIRSTW]]' ;;
-esac
-
 # Try without a prefix undercore, then with it.
 for ac_symprfx in "" "_"; do