From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 34302 invoked by alias); 7 Nov 2016 15:46:38 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 34290 invoked by uid 89); 7 Nov 2016 15:46:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=Hx-languages-length:1519, watch X-HELO: relay1.mentorg.com Date: Mon, 07 Nov 2016 15:46:00 -0000 From: Joseph Myers To: Waldemar Brodkorb CC: Adhemerval Zanella , , , Subject: Re: Building cross-toolchain for microblaze In-Reply-To: <20161106020455.GR27313@waldemar-brodkorb.de> Message-ID: References: <20161106020455.GR27313@waldemar-brodkorb.de> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2016-11/txt/msg00237.txt.bz2 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