linux-mips
[Top] [All Lists]

Re: Compile error with current CVS kernel

To: K.H.C.vanHouten@kpn.com
Subject: Re: Compile error with current CVS kernel
From: Ralf Baechle <ralf@oss.sgi.com>
Date: Tue, 13 Mar 2001 15:22:36 +0100
Cc: Adrian Bunk <bunk@fs.tum.de>, linux-mips@oss.sgi.com, K.H.C.vanHouten@research.kpn.com
In-reply-to: <200103130746.IAA07580@sparta.research.kpn.com>; from K.H.C.vanHouten@research.kpn.com on Tue, Mar 13, 2001 at 08:46:43AM +0100
References: <20010313001520.A20673@bacchus.dhis.org> <200103130746.IAA07580@sparta.research.kpn.com>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.2.5i
On Tue, Mar 13, 2001 at 08:46:43AM +0100, Houten K.H.C. van (Karel) wrote:

> Hope this helps.

Against my low blood pressure - yes ...

>     LOAD off    0x0000000000000000 vaddr 0x0000000000001000 paddr 
> 0x0000000000001000 align 2**12
>          filesz 0x000000000000a184 memsz 0x000000000000a184 flags r--

This PT_LOAD entry shouldn't even exist ...

>     LOAD off    0x000000000000b000 vaddr 0xffffffff88002000 paddr 
> 0xffffffff88002000 align 2**12
>          filesz 0x00000000001acd10 memsz 0x00000000001d25a4 flags rwx


>  15 .kstrtab      00007c24  0000000000001b00  0000000000001b00  00000b00  2**2
>                   CONTENTS, ALLOC, LOAD, READONLY, DATA
>  16 __ksymtab     00001a60  0000000000009724  0000000000009724  00008724  2**2
>                   CONTENTS, ALLOC, LOAD, READONLY, DATA

That's scary - these sections are explicitly mentioned in the linker
script and yet ld places them near address zero.  Oh pleassure, oh
garbage.

This can probably be fixed by changing the ldscript; can experiment what
it takes to get your ld to place all sections with a LOAD attribute placed
next to each other?  My ld behaves fine.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>