From: Karel van Houten <K.H.C.vanHouten@research.kpn.com>
To: ralf@oss.sgi.com (Ralf Baechle)
Cc: bunk@fs.tum.de (Adrian Bunk), linux-mips@oss.sgi.com
Subject: Re: Compile error with current CVS kernel
Date: Tue, 13 Mar 2001 19:18:05 +0100 (MET) [thread overview]
Message-ID: <200103131818.TAA14585@sparta.research.kpn.com> (raw)
In-Reply-To: <20010313152236.B1208@bacchus.dhis.org>
Hi Ralf,
Ralf wrote:
>
> 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.
Can you point me to a binutils version and/or patches that should
behave OK for native compiles?
--
Karel van Houten
----------------------------------------------------------
The box said "Requires Windows 95 or better."
I can't understand why it won't work on my Linux computer.
----------------------------------------------------------
WARNING: multiple messages have this Message-ID (diff)
From: Karel van Houten <K.H.C.vanHouten@research.kpn.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Adrian Bunk <bunk@fs.tum.de>, linux-mips@oss.sgi.com
Subject: Re: Compile error with current CVS kernel
Date: Tue, 13 Mar 2001 19:18:05 +0100 (MET) [thread overview]
Message-ID: <200103131818.TAA14585@sparta.research.kpn.com> (raw)
Message-ID: <20010313181805.Kvaasaloi07ew4sdRT30L_1d6-rSNEvosSmUsOkr7tY@z> (raw)
In-Reply-To: <20010313152236.B1208@bacchus.dhis.org>
Hi Ralf,
Ralf wrote:
>
> 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.
Can you point me to a binutils version and/or patches that should
behave OK for native compiles?
--
Karel van Houten
----------------------------------------------------------
The box said "Requires Windows 95 or better."
I can't understand why it won't work on my Linux computer.
----------------------------------------------------------
next prev parent reply other threads:[~2001-03-13 18:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 21:56 Compile error with current CVS kernel Adrian Bunk
2001-03-12 21:56 ` Adrian Bunk
2001-03-12 23:15 ` Ralf Baechle
2001-03-12 23:15 ` Ralf Baechle
2001-03-13 7:46 ` Houten K.H.C. van (Karel)
2001-03-13 13:53 ` Ralf Baechle
2001-03-13 14:22 ` Ralf Baechle
2001-03-13 18:18 ` Karel van Houten [this message]
2001-03-13 18:18 ` Karel van Houten
2001-03-13 18:27 ` Ralf Baechle
2001-03-13 18:27 ` Ralf Baechle
2001-03-13 18:38 ` Karel van Houten
2001-03-13 18:38 ` Karel van Houten
2001-03-13 18:40 ` Karel van Houten
2001-03-13 18:40 ` Karel van Houten
2001-03-13 21:15 ` Pete Popov
2001-03-21 17:39 ` Adrian Bunk
2001-03-21 17:39 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200103131818.TAA14585@sparta.research.kpn.com \
--to=k.h.c.vanhouten@research.kpn.com \
--cc=bunk@fs.tum.de \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox