From: Scott A McConnell <samcconn@cotw.com>
To: linux-mips@oss.sgi.com
Subject: Re: Link problems with 2.4.3 kernel
Date: Tue, 17 Apr 2001 10:48:33 -0700 [thread overview]
Message-ID: <3ADC81F1.72309FD0@cotw.com> (raw)
In-Reply-To: 3ADB5181.BCE02A9@cotw.com
Scott A McConnell wrote:
> No matter what I do I can not get _ftext to appear at 80001000. I use
> identical ld.scripts for bother kernels.
> At first I thought it was my binutils so I switched to the same tools
> that I used with my 2.4.0-test5 kernel.
>
> Addresses appear to be off by 0x1000. Which is why my 2.4.3 kernel dies
> on the jump to init_arch out of kernel_entry.
>
> Any thoughts about what I might be doing wrong?
>
> Thanks,
> Scott
I tracked it down to a missing:
ifdef LOADADDR
LINKFLAGS += -Ttext $(word 1,$(LOADADDR))
endif
in arch/mips/Makefile
I have no idea who added it or removed it.
I also am forced to edit the ld.script file to replace the LOADADDR
inserted with sed with 80000000.
Am I suppose to be accomplishing what I did above some other way?
Scott
prev parent reply other threads:[~2001-04-17 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 20:09 Link problems with 2.4.3 kernel Scott A McConnell
2001-04-17 16:32 ` Ralf Baechle
2001-04-17 17:48 ` Scott A McConnell [this message]
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=3ADC81F1.72309FD0@cotw.com \
--to=samcconn@cotw.com \
--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