From: David Daney <ddaney@avtrex.com>
To: Kurt Schwemmer <kurts@vitesse.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: Cross compile kernel w/ buildroot toolchain
Date: Mon, 13 Mar 2006 13:16:31 -0800 [thread overview]
Message-ID: <4415E12F.1050603@avtrex.com> (raw)
In-Reply-To: <389E6A416914954182ECDFCD844D8269434FC1@MX-COS.vsc.vitesse.com>
Kurt Schwemmer wrote:
> I didn't touch any of the source yet.
>
> I'm downloading the 1/10/05 2.6.15 tarball (
> ftp://ftp.linux-mips.org/pub/linux/mips/kernel/v2.6/linux-2.6.15.tar.gz
> )now to see if that fixes things.
>
> In response to Thiemo's message the error with (V=1) is:
>
> make -f scripts/Makefile.build obj=arch/mips/kernel
> /klocal/buildroot/build_mipsel/staging_dir/bin/mipsel-linux-gcc
> -Wp,-MD,arch/mips/kernel/.entry.o.d -nostdinc -isystem
> /klocal/buildroot/build_mipsel/staging_dir/bin-ccache/../lib/gcc/mipsel-
> linux-uclibc/3.4.5/include -D__KERNEL__ -Iinclude -D__ASSEMBLY__ -I
> /usr/local/src/linux-2.6/include/asm/gcc -G 0 -mno-abicalls -fno-pic
> -pipe -finline-limit=100000 -mabi=32 -march=mips32r2 -Wa,-32
> -Wa,-march=mips32r2 -Wa,-mips32r2 -Wa,--trap
> -Iinclude/asm-mips/mach-mips -Iinclude/asm-mips/mach-generic -Wall
> -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
> -ffreestanding -O2 -fomit-frame-pointer -I
> /usr/local/src/linux-2.6/include/asm/gcc -G 0 -mno-abicalls -fno-pic
> -pipe -finline-limit=100000 -mabi=32 -march=mips32r2 -Wa,-32
> -Wa,-march=mips32r2 -Wa,-mips32r2 -Wa,--trap
> -Iinclude/asm-mips/mach-mips -Iinclude/asm-mips/mach-generic -c -o
> arch/mips/kernel/entry.o arch/mips/kernel/entry.S
> arch/mips/kernel/entry.S: Assembler messages:
> arch/mips/kernel/entry.S:157: Error: opcode not supported on this
> processor: mips32 (mips32) `jr.hb $31'
> make[1]: *** [arch/mips/kernel/entry.o] Error 1
> make: *** [arch/mips/kernel] Error 2
>
> Also, assembler -v output:
> GNU assembler version 2.16.1 (mipsel-linux-uclibc) using BFD version
> 2.16.1
>
> Thanks,
> Kurt Schwemmer
>
You could try using crosstool to generate the compiler instead of buildroot.
Also try passing -v to gcc, that will cause it to show the exact options
that it is passing to gas. Perhaps that would shed some light on things.
David Daney
next prev parent reply other threads:[~2006-03-13 21:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 21:07 Cross compile kernel w/ buildroot toolchain Kurt Schwemmer
2006-03-13 21:07 ` Kurt Schwemmer
2006-03-13 21:16 ` David Daney [this message]
2006-03-13 21:25 ` Thiemo Seufer
-- strict thread matches above, loose matches on Subject: below --
2006-03-13 22:03 Kurt Schwemmer
2006-03-13 22:03 ` Kurt Schwemmer
2006-03-13 20:39 Kurt Schwemmer
2006-03-13 20:39 ` Kurt Schwemmer
2006-03-13 20:45 ` Ralf Baechle
2006-03-13 20:56 ` Ralf Baechle
2006-03-13 20:17 Kurt Schwemmer
2006-03-13 20:17 ` Kurt Schwemmer
2006-03-13 20:33 ` Ralf Baechle
2006-03-13 20:48 ` Thiemo Seufer
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=4415E12F.1050603@avtrex.com \
--to=ddaney@avtrex.com \
--cc=kurts@vitesse.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.