From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 128598 invoked by alias); 4 Nov 2016 13:08:44 -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 128577 invoked by uid 89); 4 Nov 2016 13:08:43 -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=expectation X-HELO: relay1.mentorg.com Date: Fri, 04 Nov 2016 13:08:00 -0000 From: Joseph Myers To: Adhemerval Zanella CC: Subject: Re: Building cross-toolchain for microblaze In-Reply-To: Message-ID: References: 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/msg00153.txt.bz2 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). -- Joseph S. Myers joseph@codesourcery.com