From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 112514 invoked by alias); 29 Jun 2017 15:29:30 -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 112440 invoked by uid 89); 29 Jun 2017 15:29:29 -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:1427 X-HELO: relay1.mentorg.com Date: Thu, 29 Jun 2017 15:29:00 -0000 From: Joseph Myers To: Vineet Gupta CC: "libc-alpha @ sourceware . org" , , Subject: Re: [RFC 4/6] ARC: Initial port to glibc In-Reply-To: <5a738e1a-fac6-3dbb-3c3f-744b12966dd7@synopsys.com> Message-ID: References: <1498550454-3560-1-git-send-email-vgupta@synopsys.com> <1498550454-3560-5-git-send-email-vgupta@synopsys.com> <5a738e1a-fac6-3dbb-3c3f-744b12966dd7@synopsys.com> 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: 2017-06/txt/msg01559.txt.bz2 On Thu, 29 Jun 2017, Vineet Gupta wrote: > I regenerated the ABI files, but it seems generated libc abilist is lacking > malloc_{get,set}_stated and had to be added manually - which causes a > subsequent testsuite failure. Is this (manual addition of entries to abi file) > correct or is this a deficiency of ARC port. malloc_get_state and malloc_set_state have been obsoleted, meaning that they are not included in any new ports, are not included in static libc for any port and in shared libc in existing ports they are compat symbols that new binaries can't be linked against. (Yes, the testsuite work to support ports postdating that obsoletion is still needed.) > Speaking of testsuite, since this is bootstrapping a glibc system we have to > resort to using scripts/cross-test-ssh.sh which is a serious pain in the neck. > Is there no easy way to build the whole test suite first and then just run it > on target. You can probably build the testsuite with "make check" without setting test-wrapper, presuming you've fixed all issues with compilation of the testsuite, then rerun "make check" with test-wrapper specified to run the execution tests. I don't know whether transferring the build directory to a different system for a native "make check" would work, but at least lots of tools would be required on the target to do so. -- Joseph S. Myers joseph@codesourcery.com