aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2003-10-08 13:52:33 +0000
committerNick Clifton <nickc@redhat.com>2003-10-08 13:52:33 +0000
commite62eb3ee7e4f8b4821b2f029d0f9d2dbbc462b44 (patch)
tree6204e6126a5e15271d39ce086bf3959ddd023322
parentafa105f875a3431f36da8bca4c1ea54e86b69c43 (diff)
downloadgdb-e62eb3ee7e4f8b4821b2f029d0f9d2dbbc462b44.zip
gdb-e62eb3ee7e4f8b4821b2f029d0f9d2dbbc462b44.tar.gz
gdb-e62eb3ee7e4f8b4821b2f029d0f9d2dbbc462b44.tar.bz2
lexsup.c (parse_args: OPTION_CALL_SHARED): Revise comment describing defaults.
Change default to report unresolved symbols in object files as well.
-rw-r--r--ld/ChangeLog6
-rw-r--r--ld/lexsup.c17
2 files changed, 14 insertions, 9 deletions
diff --git a/ld/ChangeLog b/ld/ChangeLog
index 28c6218..f12a8a8 100644
--- a/ld/ChangeLog
+++ b/ld/ChangeLog
@@ -1,3 +1,9 @@
+2003-10-08 Nick Clifton <nickc@redhat.com>
+
+ * lexsup.c (parse_args: OPTION_CALL_SHARED): Revise comment
+ describing defaults. Change default to report unresolved symbols
+ in object files as well.
+
2003-10-08 Hans-Peter Nilsson <hp@bitrange.com>
* ldexp.c (fold_name) <case DEFINED>: Set section of result to
diff --git a/ld/lexsup.c b/ld/lexsup.c
index 556a5ba..b8d0be4 100644
--- a/ld/lexsup.c
+++ b/ld/lexsup.c
@@ -661,16 +661,15 @@ parse_args (unsigned argc, char **argv)
case OPTION_CALL_SHARED:
config.dynamic_link = TRUE;
/* When linking against shared libraries, the default behaviour is
- to report any unresolved references. This is for backwards
- comptability with previous linker behaviour. Whilst strictly
- speaking it is not a failure to encounter unresolved symbols at
- link time - the symbol *might* be available at load time - it is
- nevertheless necessary for the correct execution of the autoconf
- package. (It needs to be able to detect functions that are not
- provided by the host OS). Since this package is used by lots of
- projects, maintaining the old linker behaviour is important. */
+ to report any unresolved references. Although strictly speaking
+ it is not a failure to encounter unresolved symbols at link time
+ - the symbol *might* be available at load time - it is a strong
+ indication that the resulting executable will not work. Plus it
+ is necessary for the correct execution of the autoconf package,
+ which needs to be able to detect functions that are not provided
+ by the host OS. */
if (link_info.unresolved_syms_in_objects == RM_NOT_YET_SET)
- link_info.unresolved_syms_in_objects = RM_IGNORE;
+ link_info.unresolved_syms_in_objects = how_to_report_unresolved_symbols;
if (link_info.unresolved_syms_in_shared_libs == RM_NOT_YET_SET)
link_info.unresolved_syms_in_shared_libs = how_to_report_unresolved_symbols;
break;