On Fri, Jul 20, 2007 at 04:07:21PM +0200, Jan Dittmer wrote: > Paul Mundt wrote: > >Paul Mundt (5): > > sh64: Wire up fallocate() syscall. > > sh64: Update cayman defconfig. > > sh64: Fix up PCI section mismatch warnings. > > sh64: Move entry point code to .text.head. > > sh64: Flag sh64_get_page() as __init_refok. > > Tangential question. Which is the currently recommended cross toolchain > for sh64? With "gcc 3.2 20020529", "binutils 020306 20030206" (some > binary toolchain from ~2 years ago somewhere off the web) I get [1] > > CC fs/seq_file.o > CC fs/xattr.o > fs/xattr.c: In function `vfs_listxattr': > fs/xattr.c:161: unrecognizable insn: > (insn 162 159 114 (set (subreg:DI (reg:SI 181) 0) > (reg:DI 182)) -1 (nil) > (nil)) > fs/xattr.c:161: Internal compiler error in get_attr_highpart, at > insn-attrtab.c:6211 > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. > make[2]: *** [fs/xattr.o] Error 1 > make[1]: *** [fs] Error 2 > make: *** [_all] Error 2 > > gcc 3.4.x, 4.0.x, 4.1.x don't build for me from source > (target -superh-linux-gnu, binutils 2.15.x or 2.17.x).
I've been using sh64-linux targetted toolchains created from the gentoo crossdev, which works fine with stock versions. I can send you a tarball of the toolchain off-list if you like. Applications are still in a pretty questionable state with recent compilers, but the kernel does hold up well enough. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
