Building cross-toolchain for microblaze

Waldemar Brodkorb wbx@openadk.org
Sun Nov 6 02:05:00 GMT 2016


Hi,
Joseph Myers wrote,

> On Fri, 4 Nov 2016, Adhemerval Zanella wrote:
> 
> > I could build a workable toolchain, at least for glibc building, by
> > configuring GCC with both '--disable-sjlj-exceptions'  and 
> > '--disable-shared'.  I did not dig into the issue, but it was already
> > reported on maillist this same issue.
> 
> The *first* GCC works to build glibc.  The problem is with the second one, 
> with shared libraries and C++ support (and separate libgcc_eh, which is 
> what actually results in the undefined references), since you want to 
> rebuild with such a second compiler before running the testsuite (the 
> expectation is that a bootstrap compiler will produce a correct glibc, but 
> not a build tree suitable for testing in).

Some projects as Buldroot using some gcc patches which are not in
upstream gcc to provide Dwarf:

https://git.busybox.net/buildroot/tree/package/gcc/5.4.0/840-microblaze-enable-dwarf-eh-support.patch

This allows to build a microblaze toolchain.

best regards
 Waldemar



More information about the Libc-alpha mailing list