Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Carsten Langgaard <carstenl@mips.com>
To: Muthukumar Ratty <muthur@paul.rutgers.edu>
Cc: linux-mips@oss.sgi.com
Subject: Re: Cross toolchain problem??
Date: Sat, 02 Mar 2002 09:38:41 +0100	[thread overview]
Message-ID: <3C808F91.D9B5DC6D@mips.com> (raw)
In-Reply-To: Pine.SOL.4.10.10203012316030.9292-100000@paul.rutgers.edu

Muthukumar Ratty wrote:

> To add to my previous mail:
> The same code when I build with Algorithmics tool chain builds "jal
> gt64120" properly, I mean it doesnt use _gp.
>
> But I cannot stick with Algorithmics tool chain because when I build the
> kernel 2.4.3 it complains that "my Algorithmics toolchain is old and it
> builds buggy kernel."

Just remove the check from the kernel.

>
> I am really stuck here for a while and any help would be appreciated.
> Thanks a lot,
> Muthu
>
> On Fri, 1 Mar 2002, Muthukumar Ratty wrote:
>
> >
> > Hi,
> >
> > My toolchain information
> > Host : redhat linux 7.1 in a i386 PC
> >
> > Tool chains built as per Brad LaRonde's writeup.
> >  (Building a Modern MIPS Cross-Toolchain for Linux)
> > gcc: version 3.0.3
> > binutils : version 2.11.92.0.7 20011016
> > glibc: version 2.2.3 with linux threads patch and mips-base-addr patch
> >       from Brad.
> >
> > I was able to build kernel 2.4.3, I got from oss.sgi.com and it works fine
> > (thanks to everyone). So I assumed my toolchain is working fine. Next I
> > modified the yamon startup code (just used reset.S, gt64120.S, link.xn and
> > did some cleaning to get it compiled). When I tried to run srecconv.pl
> > util, I got error message "Out of memory!" (I wanto convert it into flash
> > format to download. The strange thing is, I have an Algorithmics toolchain
> > version egcs-2.90.23 980102, GNU ld 2.9.1/sde-4.0.3, and the srec I got
> > from it doesnt havethis problem)
> >
> > I tried to trace down and found that the srec generated has load
> > address 0x80001000 for data and 0xbfc00000 for the startup code (this is
> > because the link.xn is defined this way). So when an associative array is
> > used in perl script srecconv.pl, it runs out of memory.  I dont know perl
> > and I am stuck here. Can somebody point me how to proceed? thanks a lot.
> > (i really want to have the data loaded at 0x80001000 but it should be
> > initially in flash).
> >
> > So I changed the data load address to 0xbfc01000 and now the srecconv
> > works fine and I got a .fl image. But my "jal gt64120_init" is assembled
> > to use _gp and I dont think I set the _gp properly ( I am still in the
> > process of reading Dominics book:). so the code is not at all entering in
> > to the gt64120_init function. but when I change it to "j gt64120_init"
> > it works fine. (Cant I use "jal" here?)
> >
> > Any help would be appreciated and sorry for this long mail,
> > Thanks,
> > Muthu
> >
> >
> >

  reply	other threads:[~2002-03-02  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-02  2:25 Cross toolchain problem?? Muthukumar Ratty
2002-03-02  4:22 ` Muthukumar Ratty
2002-03-02  8:38   ` Carsten Langgaard [this message]
2002-03-02 14:59     ` Muthukumar Ratty
2002-03-03 11:14       ` Carsten Langgaard
2002-03-03 13:22         ` Dominic Sweetman

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=3C808F91.D9B5DC6D@mips.com \
    --to=carstenl@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=muthur@paul.rutgers.edu \
    /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