From: Nicu Popovici <octavp@isratech.ro>
To: kjlin <kj.lin@viditec-netmedia.com.tw>, linux-mips@oss.sgi.com
Subject: Re: Run the cross-compiled program.
Date: Wed, 20 Dec 2000 17:54:55 -0500 [thread overview]
Message-ID: <3A4138BF.871CB6C@isratech.ro> (raw)
In-Reply-To: 053601c06a6c$ee66ca60$056aaac0@kjlin
Hello,
I am very interested in getting the latest sources for binutils, gcc and
glibc working in cross toolchain for mips. PLease tell me from where did
you took the gcc that you use . Please give me as muche details as you
can.
Regards,
Nicu
kjlin wrote:
> Can anyone point out which step i done wrong in the process of
> cross-compiling an program with the -static option?
> I made the cross-compile toolkit by myself.
> All the source code and patches for cross-compile were downloaded from
> the SGI ftp site.
> The version is as following:
> cross-binutils = version 2.10.90
> cross-gcc = version 2.96 20000707
> cross-usable glibc = libc-2.1.90
> The cross-compile toolkits building process is ok!
> I used the cross-compiler to compile a program with the " -static "
> option in the host and then ran it on the target.
> But i got the error message:# ./a.outFATAL: kernel too old
> Aborted Where i be trapped?
> My host system is x86 running linux-2.2.14(Redhat 6.2).
> My target system is an embedded mips board running linux-2.2.14 and
> shell is the statically linked ash binary from a lib-2.6.0
> filesystem(kernel version unknown).
> By the way, i builded the cross-usable glibc-2.1.90 with configure
> "--enable-kernel=2.2.14".Thanx,KJ from kj.lin@viditec-netmedia.com.tw
next prev parent reply other threads:[~2000-12-20 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 10:09 Run the cross-compiled program kjlin
2000-12-20 10:09 ` kjlin
2000-12-20 22:54 ` Nicu Popovici [this message]
2000-12-21 2:39 ` Keith M Wesolowski
2000-12-22 6:38 ` kjlin
2000-12-22 6:38 ` kjlin
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=3A4138BF.871CB6C@isratech.ro \
--to=octavp@isratech.ro \
--cc=kj.lin@viditec-netmedia.com.tw \
--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