From: Guenter Roeck <linux@roeck-us.net>
To: Angelo Dureghello <angelo@sysam.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: issues on last 32 bit m68k toolchain
Date: Fri, 6 Feb 2015 18:07:32 -0800 [thread overview]
Message-ID: <20150207020732.GA3762@roeck-us.net> (raw)
In-Reply-To: <54D5283C.8050905@sysam.it>
On Fri, Feb 06, 2015 at 09:46:52PM +0100, Angelo Dureghello wrote:
> Dear all,
>
> i was using the public x86 32bit toolchain from kernel.org:
>
> https://www.kernel.org/pub/tools/crosstool/files/bin/i686/4.6.3/i686-gcc-4.6.3-nolibc_m68k-linux.tar.gz
>
> Unfortunately, for ColdFire arch, there is a bug in gas/binutils
> for this toolchain:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=17877
>
> Produced binaries are not working on the target.
>
> Is it possible to have available another m68k toolchain
> (including older or newer binutils/as than the bugged 2.22) ?
>
Can you try the 64 bit toolchain ?
https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.9.0/x86_64-gcc-4.9.0-nolibc_m68k-linux.tar.gz
Guenter
prev parent reply other threads:[~2015-02-07 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 20:46 issues on last 32 bit m68k toolchain Angelo Dureghello
2015-02-07 2:07 ` Guenter Roeck [this message]
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=20150207020732.GA3762@roeck-us.net \
--to=linux@roeck-us.net \
--cc=angelo@sysam.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox