From: Ralf Baechle <ralf@oss.sgi.com>
To: Karel van Houten <K.H.C.vanHouten@research.kpn.com>
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:27:11 +0100 [thread overview]
Message-ID: <20010313192711.F1208@bacchus.dhis.org> (raw)
In-Reply-To: <200103131818.TAA14585@sparta.research.kpn.com>; from K.H.C.vanHouten@research.kpn.com on Tue, Mar 13, 2001 at 07:18:05PM +0100
On Tue, Mar 13, 2001 at 07:18:05PM +0100, Karel van Houten 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?
It's not native vs. crosscompile; this problem with binutils hits in both
cases and only older versions (which aren't suitable for use with
glibc 2.2 ...) are not affected.
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@oss.sgi.com>
To: Karel van Houten <K.H.C.vanHouten@research.kpn.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:27:11 +0100 [thread overview]
Message-ID: <20010313192711.F1208@bacchus.dhis.org> (raw)
Message-ID: <20010313182711.daejfl4zLrVmefmPjZpq7pEJKyv9MlKy6QcptAg4BoM@z> (raw)
In-Reply-To: <200103131818.TAA14585@sparta.research.kpn.com>; from K.H.C.vanHouten@research.kpn.com on Tue, Mar 13, 2001 at 07:18:05PM +0100
On Tue, Mar 13, 2001 at 07:18:05PM +0100, Karel van Houten 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?
It's not native vs. crosscompile; this problem with binutils hits in both
cases and only older versions (which aren't suitable for use with
glibc 2.2 ...) are not affected.
Ralf
next prev parent reply other threads:[~2001-03-13 21:32 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
2001-03-13 18:18 ` Karel van Houten
2001-03-13 18:27 ` Ralf Baechle [this message]
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=20010313192711.F1208@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=K.H.C.vanHouten@research.kpn.com \
--cc=bunk@fs.tum.de \
--cc=linux-mips@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