From: Florian Lohoff <flo@rfc822.org>
To: Nicu Popovici <octavp@isratech.ro>
Cc: linux-mips@oss.sgi.com
Subject: Re: Still cannot compile the KERNEL!!!
Date: Mon, 30 Oct 2000 15:21:29 +0100 [thread overview]
Message-ID: <20001030152129.D2687@paradigm.rfc822.org> (raw)
In-Reply-To: <39FDAE22.7626E6E@isratech.ro>; from octavp@isratech.ro on Mon, Oct 30, 2000 at 12:21:38PM -0500
On Mon, Oct 30, 2000 at 12:21:38PM -0500, Nicu Popovici wrote:
> Hello you all,
>
> I have a problem. I've built a crosscompiler for MIPS on my intel
> machine but until now I could not compile any mips kernel. I tried with
> version from CVS site and now I an trying with
> linux-2.2.12.mips-src.01.04.tar.gz and I an running into errors from the
> beggining.( are in the attached file )
>
> I still succeded to compile a test.c file on my intel machine with my
> crosscompiler and then to run the resulted file on the mips machine and
> it worked.
> When I tried with the g++ and with the test.cpp ( a simple class ) the
> crosscompiler made a file but when I executed on the mips machine it
> says
> a.out error in loading shared libraries
> undefined simbol : _deregister_frame_info
I guess you have a broken 2.07 glibc for mips lying around - Try to eliminate
that and use the 2.06 made by ralf or start with glibc 2.2
(For experienced users)
BTW: For compiling a kernel you dont need and glibc on the cross devel machine
at all.
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
next prev parent reply other threads:[~2000-10-30 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 17:21 Still cannot compile the KERNEL!!! Nicu Popovici
2000-10-30 11:45 ` Klaus Naumann
2000-10-30 14:21 ` Florian Lohoff [this message]
2000-10-30 15:23 ` Keith M Wesolowski
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=20001030152129.D2687@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=octavp@isratech.ro \
/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