From owner-freebsd-current Fri Apr 25 10:12:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA27731 for current-outgoing; Fri, 25 Apr 1997 10:12:24 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA27726; Fri, 25 Apr 1997 10:12:17 -0700 (PDT) Received: from nlsystems.com by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0wKoXW-0009DeC; Fri, 25 Apr 97 10:12 PDT Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id SAA24440; Fri, 25 Apr 1997 18:04:01 +0100 (BST) Date: Fri, 25 Apr 1997 18:04:01 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: jdp@freebsd.org, current@freebsd.org Subject: Re: Minor fix to ld In-Reply-To: <199704251520.IAA03420@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 25 Apr 1997, Terry Lambert wrote: > > While I was writing my new kernel linker, I noticed that the > > relocation_info structures for the members of linker sets had r_length set > > to zero (indicating byte sized relocations) when the objects being > > relocated were 32bit. The code in ld.so has a hack (see the definition of > > REL_SIZE in ld/i386/md.c) to work around this. It would be nice to have > > correct relocations though and I think this patch does the job: > > Raising the object compatability red flag... Since it only appears to happen for shared libraries and since ld.so has a hack to make it completely ignore the r_length field, I am not too worried about object compatability... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891