From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-74471-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 111670 invoked by alias); 6 Nov 2016 02:05:19 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 109589 invoked by uid 89); 6 Nov 2016 02:05:08 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=Hx-languages-length:1057
X-HELO: helium.openadk.org
Date: Sun, 06 Nov 2016 02:05:00 -0000
From: Waldemar Brodkorb <wbx@openadk.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	libc-alpha@sourceware.org
Subject: Re: Building cross-toolchain for microblaze
Message-ID: <20161106020455.GR27313@waldemar-brodkorb.de>
References: <alpine.DEB.2.20.1611040240470.20687@digraph.polyomino.org.uk>
 <f5608edb-228f-da96-229e-381a387105b7@linaro.org>
 <alpine.DEB.2.20.1611041306220.1065@digraph.polyomino.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1611041306220.1065@digraph.polyomino.org.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SW-Source: 2016-11/txt/msg00224.txt.bz2

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