From: Joseph Myers <joseph@codesourcery.com>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
<libc-alpha@sourceware.org>, <david@holsgrove.tech>,
<eager@eagercon.com>
Subject: Re: Building cross-toolchain for microblaze
Date: Mon, 07 Nov 2016 15:46:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611071544090.3948@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20161106020455.GR27313@waldemar-brodkorb.de>
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:
>
> 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.
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
unnecessarily.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2016-11-07 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 2:48 Joseph Myers
2016-11-04 12:12 ` Adhemerval Zanella
2016-11-04 13:08 ` Joseph Myers
2016-11-04 13:44 ` Adhemerval Zanella
2016-11-06 2:05 ` Waldemar Brodkorb
2016-11-07 15:46 ` Joseph Myers [this message]
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=alpine.DEB.2.20.1611071544090.3948@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=david@holsgrove.tech \
--cc=eager@eagercon.com \
--cc=libc-alpha@sourceware.org \
--cc=wbx@openadk.org \
/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).