From: Jan Dittmer <jdi@l4x.org>
To: David Howells <dhowells@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Working frv toolchain?
Date: Fri, 02 Nov 2007 22:19:53 +0100 [thread overview]
Message-ID: <472B9479.7040105@l4x.org> (raw)
In-Reply-To: <15712.1193753924@redhat.com>
David Howells wrote:
> David Howells <dhowells@redhat.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
next prev parent reply other threads:[~2007-11-02 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 10:26 Working frv toolchain? Jan Dittmer
2007-10-29 13:06 ` David Howells
2007-10-29 19:24 ` Jan Dittmer
2007-10-30 14:17 ` David Howells
2007-10-30 14:18 ` David Howells
2007-10-30 16:06 ` Jan Dittmer
2007-11-02 21:19 ` Jan Dittmer [this message]
2007-11-03 10:58 ` David Howells
2007-11-04 15:54 ` Jan Dittmer
2007-11-05 16:04 ` David Howells
2007-11-06 21:05 ` Jan Dittmer
2007-11-06 21:47 ` David Howells
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=472B9479.7040105@l4x.org \
--to=jdi@l4x.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.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.