From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: crossgcc@sourceware.org, linz@li-pro.net
Cc: David Holsgrove <david.holsgrove@xilinx.com>,
Nagaraju <nmekala@xilinx.com>
Subject: Re: [PATCH] arch/microblaze: add new architecture
Date: Wed, 03 Oct 2012 21:48:00 -0000 [thread overview]
Message-ID: <201210032348.15569.yann.morin.1998@free.fr> (raw)
In-Reply-To: <1349256842.2990.66.camel@keto>
Stephan, David, Nagaraju, All,
On Wednesday 03 October 2012 11:34:02 Stephan Linz wrote:
> Am Sonntag, den 23.09.2012, 00:38 +0200 schrieb Yann E. MORIN:
> > On Thursday 20 September 2012 06:04:30 David Holsgrove wrote:
> > > # HG changeset patch
> > > # User David Holsgrove <david.holsgrove@xilinx.com>
> > > # Date 1348113698 -36000
> > > # Node ID 9c93e18b3d68b19303f37bf604c0ad907451872a
> > > # Parent 06b663f297adb76149f089136a78e7d5999c63bd
> > > arch/microblaze: add new architecture
> >
> > Applied as #7e41a188bd7c. Thank you!
> are there more patches in queue to submit?
As was stated in the commit log, microblaze support is in the process of
being pushed upstream for the different components impacted:
---8<---
This depends on EXPERIMENTAL, as upstream projects do not yet
include full support to build a modern microblaze compiler.
This is in the process of being updated, but is not currently
publicly accessible.
---8<---
Thus, it is expected that the build fails.
David said he'd provide sample defconfigs as soon as he knows the
versions of each components that have microblaze support.
In the meantime, you may want to sneak the Xilinx' binutils, gcc, eglibc
and linux, (from the tree you pointed above) in place of the upstream ones:
ct-ng menuconfig <- prepare the versions matching the
ones in the Xilinx tree
ct-ng +libc_check_config <- this will extract everything
cd .build/src <- remove the binutils, gcc, eglibc and
linux dirs, and substitute with the
Xilinx ones
cd ../..
ct-ng build <- restart the build, now with the Xilinx'
sources
No promise on buildability. YMMV, as they use to say...
Of course, David and Nagaraju. if I talked with my ass, feel free to
correct me.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-10-03 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 4:04 David Holsgrove
2012-09-22 22:38 ` Yann E. MORIN
2012-10-03 9:34 ` Stephan Linz
2012-10-03 21:48 ` Yann E. MORIN [this message]
2012-10-04 2:01 ` David Holsgrove
2012-10-04 22:04 ` Stephan Linz
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=201210032348.15569.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=crossgcc@sourceware.org \
--cc=david.holsgrove@xilinx.com \
--cc=linz@li-pro.net \
--cc=nmekala@xilinx.com \
/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).