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: microblaze-unknown-linux-gnu : cross-gdb failed


Hi Stephan, All

> -----Original Message-----
> From: Stephan Linz [mailto:linz@li-pro.net]
> Sent: Sunday, 7 October 2012 10:25 pm
> To: David Holsgrove; Nagaraju Mekala
> Cc: crossgcc
> Subject: microblaze-unknown-linux-gnu : cross-gdb failed
> 
> Hi David, Nagaraju and All
> 
> 
> first of all, based on Davids patch to use customized source trees for
> binutils/gcc/eglibs I've successfully rebuild the sources presented on
> git.xilinx.com page (see description below on the end).
> 

Glad to hear you've had success this far :-)

> Now I run into a problem with cross-gdb I'll try to fix together with
> the maintainer from Xilinx and Crosstool-NG.
> 
> The cross-gdb step breaks with the following message:
> [INFO ]  Installing cross-gdb
> [ERROR]    /store/devel/TOOLCHAINS/crosstool-ng/targets/src/gdb-
> custom/gdb/../opcodes/../opcodes/microblaze-opcm.h:34: error: 'sleep'
> redeclared as different kind of symbol
> [ERROR]    make[3]: *** [microblaze-tdep.o] Error 1
> [ERROR]    make[2]: *** [all-gdb] Error 2
> [ERROR]    make[1]: *** [all] Error 2
> 
[SNIP]

This unfortunately confirms what I suspected, that the source on git.xilinx.com is out of date. We'll look into updating what has been made available.

The error you are seeing is indeed caused by the inclusion of 'sleep' in microblaze_instr in the gdb/opcodes/microblaze-opcm.h. It would appear the version of microblaze-opcm.h on git.xilinx.com is incorrect - it should match the binutils version, and not specify 'sleep', as this is simply an alias of the mbar 16 instruction.

If you would like to manually remove this entry, you should be able to build cross-gdb successfully without any conflicts.

[SNIP]
> NOTE: I've no yet tried to compile real application code with the
> rebuilded tool chain. That's all EXPERIMENTAL!
> 
> 
> @David and Nagaraju: Is there a time line to merge all the Microblaze
> portings into binutils/gcc/eglibc mainline or present patch sets for
> crosstool-ng in a short time?
> 

I'd rather not bombard crosstool-ng with heavy patches for adding mb support, so in the meantime building custom against git.xilinx.com is probably the best strategy. I donât have an exact time line for mainline availability, but submissions based on latest branches of binutils/gdb/gcc/eglibc/newlib will begin shortly to the relevant mailing lists.

Thanks again,
David

> 
> --
> Best regards,
> Stephan Linz
> ______________________________________________________________________________
> MB-Ref: http://www.li-pro.de/xilinx_mb:mbref:start
> OpenDCC: http://www.li-pro.net/opendcc.phtml
> PC/M: http://www.li-pro.net/pcm.phtml
> Sourceforge: http://sourceforge.net/users/slz
> Gitorious: https://gitorious.org/~slz
> 




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