This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See crosstool-NG for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] arch/microblaze: add new architecture


Hi Stephan, Yann, All

On 4 October 2012 07:48, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> 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.
>

Yann's correct Stephan, there are no other microblaze specific patches
for crosstool-NG queued
for submission, aside from the sample defconfigs which I cant submit
yet without knowing the
version numbers.

I'll speak with Nagaraju with regards the source we're hosting on the
git.xilinx.com page, I believe it
may need updating. There are build scripts and sample configs there
which should build against
the source tarballs we're providing as a stop gap until microblaze
support is added / updated in
mainline.

> 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...
>

I have a feature patch which I'll send to the list now which addresses
this custom source build scenario Yann.
Its modelled on the existing linux custom functionality, so I'm hoping
it can be included to make development /
building of manually revision controlled source easier.

> Of course, David and Nagaraju. if I talked with my ass, feel free to
> correct me.
>

Not at all Yann, thanks for the reply :-)

David

> 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
>

--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]