[prev in list] [next in list] [prev in thread] [next in thread] 

List:       binutils
Subject:    ld documentation update
From:       "Ralf Habacker" <ralf.habacker () freenet ! de>
Date:       2005-02-27 12:43:00
Message-ID: 001c01c51cc9$e0394120$0300a8c0 () P5
[Download RAW message or body]

Hi,

I just reread the documentation of ld and found a bug in the win32 section 
of the ld documentation.
Changelog entry and patch is applied.

Regards

Ralf


2005-02-27  Ralf Habacker  <ralf.habacker@freenet.de>

        * ld.texinfo: (Machine dependend/Win32):Removed uncorrect documented
        limitation of direct linking to dll feature.

Index: ld.texinfo
===================================================================
RCS file: /cvs/src/src/ld/ld.texinfo,v
retrieving revision 1.140
diff -u -3 -p -B -r1.140 ld.texinfo
--- ld.texinfo  1 Feb 2005 17:31:01 -0000       1.140
+++ ld.texinfo  27 Feb 2005 12:34:45 -0000
@@ -5669,12 +5669,8 @@ even when auto-import features are exerc
 @samp{--enable-runtime-pseudo-relocs} is used.

 Given the improvements in speed and memory usage, one might justifiably
-wonder why import libraries are used at all.  There are two reasons:
-
-1. Until recently, the link-directly-to-dll functionality did @emph{not}
-work with auto-imported data.
-
-2. Sometimes it is necessary to include pure static objects within the
+wonder why import libraries are used at all.  The reason is, that sometimes
+it is necessary to include pure static objects within the
 import library (which otherwise contains only bfd's for indirection
 symbols that point to the exports of a dll).  Again, the import lib
 for the cygwin kernel makes use of this ability, and it is not


[prev in list] [next in list] [prev in thread] [next in thread]