From: Angelo Dureghello <angelo@sysam.it>
To: u-boot@lists.denx.de
Subject: [U-Boot] m68k: Build problems on some boards
Date: Tue, 02 Dec 2014 00:17:33 +0100 [thread overview]
Message-ID: <547CF70D.8070101@sysam.it> (raw)
In-Reply-To: <547CD297.4080002@sysam.it>
Hi,
i was be able to compile all the m68k boards (if i
grepp'ed well).
In total 22 boards, and 36 defconfigs.
astro_mcf5373l.h
cobra5272.h
eb_cpu5282.h
gr_cpci_ax2000.h
TASREG.h
M5208EVBE.h
M52277EVB.h
M5235EVB.h
M5249EVB.h
M5253DEMO.h
M5253EVBE.h
M5272C3.h
M5275EVB.h
M5282EVB.h
M53017EVB.h
M5329EVB.h
M5329AFEE_defconfig
M5329BFEE_defconfig
M5373EVB.h
M54418TWR.h
M54451EVB.h
M54455EVB.h
M5475EVB.h
M5475AFE_defconfig
M5475BFE_defconfig
M5475CFE_defconfig
M5475DFE_defconfig
M5475EFE_defconfig
M5475FFE_defconfig
M5475GFE_defconfig
M5485EVB.h
M5485AFE_defconfig
M5485BFE_defconfig
M5485CFE_defconfig
M5485DFE_defconfig
M5485EFE_defconfig
M5485FFE_defconfig
M5485GFE_defconfig
M5485HFE_defconfig
The toolchain i used is:
m68k-elf-gcc (Sourcery CodeBench Lite 2011.09-21) 4.6.1
This toolchain was downloadable from Code Sourcery (Mentor) site some
years ago, but actually seems not downloadable anymore.
I would like to setup a wiki page and share it as downloadable but i am
not sure this is legal. I am investigating.
Regards,
Angelo
next prev parent reply other threads:[~2014-12-01 23:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 20:41 [U-Boot] m68k: Build problems on some boards Angelo Dureghello
2014-12-01 23:17 ` Angelo Dureghello [this message]
2014-12-02 4:26 ` Masahiro Yamada
2014-12-02 9:22 ` Angelo Dureghello
2014-12-15 16:46 ` Masahiro YAMADA
2014-12-22 18:06 ` Angelo Dureghello
2015-01-26 20:54 ` Angelo Dureghello
-- strict thread matches above, loose matches on Subject: below --
2014-06-15 12:57 Vasili Galka
2014-06-22 9:19 ` Vasili Galka
2014-06-23 13:10 ` Tom Rini
2014-07-22 3:38 ` Masahiro Yamada
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=547CF70D.8070101@sysam.it \
--to=angelo@sysam.it \
--cc=u-boot@lists.denx.de \
/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