linux-kernel - Re: Working frv toolchain?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <472B9479.7040105@l4x.org>
Date:	Fri, 02 Nov 2007 22:19:53 +0100
From:	Jan Dittmer <jdi@....org>
To:	David Howells <dhowells@...hat.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Working frv toolchain?

David Howells wrote:
> David Howells <dhowells@...hat.com> wrote:
> 
>> Ah... I'd forgotten about that.  I'm not sure all the ASM constraint changes
>> are upstream yet, and gcc bz 28583 also gets incurred.  Are you particularly
>> interested in building your own compiler, or would one of ours do?
> 
> Look in:
> 
> 	ftp://ftp.redhat.com/pub/redhat/gnupro/FRV

Hrm, that gets me further, but one of the final stages fail:

   CC      init/version.o
   LD      init/built-in.o
   LD      .tmp_vmlinux1
kernel/built-in.o(.text+0x2e684): In function `kallsyms_lookup_name':
: relocation truncated to fit: R_FRV_GPREL12 kallsyms_num_syms
kernel/built-in.o(.text+0x2e6d4): In function `kallsyms_lookup_name':
: relocation truncated to fit: R_FRV_GPREL12 kallsyms_num_syms
kernel/built-in.o(.text+0x2e750): In function `get_symbol_pos':
: relocation truncated to fit: R_FRV_GPREL12 kallsyms_num_syms
kernel/built-in.o(.text+0x2ed00): In function `update_iter':
: relocation truncated to fit: R_FRV_GPREL12 kallsyms_num_syms
make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [sub-make] Error 2

Todays git tree. Is there any known good release I can test
this toolchain against?

Thanks,

Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/