* ChangeLog-9197: Fix typos.
* NEWS: Likewise. * ld.texinfo: Likewise. * ldlang.c: Fix comment typos.
This commit is contained in:
parent
2e0d1c66f5
commit
07f3b6ad4a
@ -1,3 +1,10 @@
|
||||
2003-10-25 Kazu Hirata <kazu@cs.umass.edu>
|
||||
|
||||
* ChangeLog-9197: Fix typos.
|
||||
* NEWS: Likewise.
|
||||
* ld.texinfo: Likewise.
|
||||
* ldlang.c: Fix comment typos.
|
||||
|
||||
2003-10-24 H.J. Lu <hongjiu.lu@intel.com>
|
||||
|
||||
* ldlang.c (lang_vers_match): Fix a typo.
|
||||
|
@ -7574,7 +7574,7 @@ Tue Oct 8 16:00:57 1991 Per Bothner (bothner at cygnus.com)
|
||||
* Makefile.in: Add LIB_PATH macro, which if set is used to replace
|
||||
the SEARCH_DIR commands in the scripts (using ugly sed magic).
|
||||
This is primarily intended for cross-linking, where you would
|
||||
place libaries in a different place than native libraries.
|
||||
place libraries in a different place than native libraries.
|
||||
Also, emulations made from ldtemplate now use $(srcdir).
|
||||
* scripttempl/ldglda29k.sc: Change SEARCH_DIR commands to a
|
||||
conventional form; people can use the Makefile's LIB_PATH to
|
||||
|
2
ld/NEWS
2
ld/NEWS
@ -200,7 +200,7 @@ Changes in version 2.5:
|
||||
|
||||
* The linker now supports linking against SunOS shared libraries. It still can
|
||||
not link SunOS PIC (Position Independent Code) files, so it can not be used to
|
||||
generate shared libaries.
|
||||
generate shared libraries.
|
||||
|
||||
* The linker now supports linking against ELF shared libraries for the i386
|
||||
(UnixWare) and SPARC (Solaris). It can also link ELF PIC files, and can be
|
||||
|
@ -884,7 +884,7 @@ lookup caching possible.
|
||||
|
||||
@item defs
|
||||
Disallows undefined symbols in object files. Undefined symbols in
|
||||
shared libaries are still allowed.
|
||||
shared libraries are still allowed.
|
||||
|
||||
@item initfirst
|
||||
This option is only meaningful when building a shared object.
|
||||
|
@ -2923,8 +2923,8 @@ lang_size_sections_1
|
||||
/* By default this is an error rather than just a
|
||||
warning because if we allocate the section to the
|
||||
default memory region we can end up creating an
|
||||
excessivly large binary, or even seg faulting when
|
||||
attmepting to perform a negative seek. See
|
||||
excessively large binary, or even seg faulting when
|
||||
attempting to perform a negative seek. See
|
||||
http://sources.redhat.com/ml/binutils/2003-04/msg00423.html
|
||||
for an example of this. This behaviour can be
|
||||
overridden by the using the --no-check-sections
|
||||
|
Loading…
Reference in New Issue
Block a user