From: Mike Frysinger <vapier@gentoo.org>
To: Huacai Chen <chenhuacai@gmail.com>
Cc: Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: custom kernel on lemote-3a-itx (Loongson-3A) crashes in userspace
Date: Thu, 26 Feb 2015 03:14:25 -0500 [thread overview]
Message-ID: <20150226081425.GR6655@vapier> (raw)
In-Reply-To: <CAAhV-H5+kQm_qAz7DLV4Rk9EqB4xJjmu1NV7kKd46aneKFZO-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
On 26 Feb 2015 15:47, Huacai Chen wrote:
> Please try the toolchain here:
> http://dev.lemote.com/files/resource/toolchain/cross-compile/
thanks, but that's kind of dodgy and kind of defeats what i'm going for ;)
- looks like binary-only
- they're x86_64 binaries (i'm doing everything native here, so mips/n32)
- is pretty old (gcc-4.5 / gcc-4.6 / binutils-2.21 / binutils-2.22)
that said, i installed Debian/mipsel(o32) into a chroot. building with the same
sources & configs yielded a kernel that seems to be running OK -- i'm on
mainline linux-3.19 now. it too has an old toolchain: binutils-2.22 and
gcc-4.6.4. i guess there's a miscompilation / the kernel sources have problems
with newer gcc versions.
installing older binutils in Gentoo was pretty easy, but trying to do gcc-4.6
ran into an ICE while bootstrapping. but at least it'll be easy to rule out
weird assembler/linker problems.
might try to put together a script to rebuild the objects one-by-one with the
newer compiler to try and narrow down the problem in the source.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-26 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 19:46 custom kernel on lemote-3a-itx (Loongson-3A) crashes in userspace Mike Frysinger
2015-02-26 7:47 ` Huacai Chen
2015-02-26 8:14 ` Mike Frysinger [this message]
2015-02-27 13:37 ` Huacai Chen
2015-02-27 20:31 ` Mike Frysinger
2015-02-28 1:29 ` Huacai Chen
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=20150226081425.GR6655@vapier \
--to=vapier@gentoo.org \
--cc=chenhuacai@gmail.com \
--cc=linux-mips@linux-mips.org \
/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