From: Joachim Nilsson <jocke@vmlinux.org>
To: crossgcc@sourceware.org
Subject: croostool-ng: GCC 4.4.1 Working!
Date: Sun, 06 Sep 2009 11:01:00 -0000 [thread overview]
Message-ID: <4AA39681.6040902@vmlinux.org> (raw)
Hi everybody!
I managed to get a working armeb-unknown-linux-uclibc toolchain using
GCC v4.4.1 today. Yay! :)
We have an Intel IXP465 based CPU board at work that I'm currently
targeting with my work, but we also have an i.MX27 and sonn possibly
Arm11 based ones as well. So I'll be working with crosstool-ng quite a
bit during the fall and winter months.
Anyway, I used the latest head (correct hg terminology?) of crosstool-ng
and added the 4.4.1 GCC patches from buildroot:
http://git.buildroot.net/buildroot/tree/toolchain/gcc/4.4.1
That's about it.
How would I proceed in contributing these patches, inline attachments,
publish a Mercurial branch, or is it sufficient with the above pointer?
Just curious for any future contributions really.
Regards
/Jocke
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2009-09-06 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 11:01 Joachim Nilsson [this message]
2009-09-26 15:28 ` Joachim Nilsson
2009-09-26 20:20 ` Yann E. MORIN
2009-09-28 13:40 ` Joachim Nilsson
2009-09-28 17:30 ` Yann E. MORIN
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=4AA39681.6040902@vmlinux.org \
--to=jocke@vmlinux.org \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).