This is the mail archive of the mailing list for the glibc project.

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: Building cross-toolchain for microblaze

On Sun, 6 Nov 2016, Waldemar Brodkorb wrote:

> 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:
> This allows to build a microblaze toolchain.

David, can you get this patch (or equivalent) upstream so that we can have 
a clean baseline for all-ABI glibc builds and compile-only tests given 
recent-enough GCC?  When people / bots are running builds of over 60 
different glibc variants to watch for regressions, requiring 
architecture-specific non-upstream patches complicates things 

Joseph S. Myers

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