to correct place.
* doc/libtool.texi (libtool script contents): update description
of global_symbol_to_cdecl.
-2004-09-23 Gary V. Vaughan <gary@gnu.org>
+2004-09-23 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
+
+ * 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 <gary@gnu.org>
* configure.ac (M4SH): AC_SUBST m4sh expander.
* config/general.m4sh, config/getopt.m4sh: New files with factored
$
@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
;;
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.
;;
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