From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9784 Path: news.gmane.org!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: Libc-Test: Tests failing on Ubuntu VM Date: Wed, 30 Mar 2016 18:47:37 +0200 Message-ID: <20160330164737.GL9862@port70.net> References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1459356479 21136 80.91.229.3 (30 Mar 2016 16:47:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 30 Mar 2016 16:47:59 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9797-gllmg-musl=m.gmane.org@lists.openwall.com Wed Mar 30 18:47:54 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1alJHd-0003MI-SZ for gllmg-musl@m.gmane.org; Wed, 30 Mar 2016 18:47:53 +0200 Original-Received: (qmail 28305 invoked by uid 550); 30 Mar 2016 16:47:50 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 28286 invoked from network); 30 Mar 2016 16:47:49 -0000 Mail-Followup-To: musl@lists.openwall.com Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Xref: news.gmane.org gmane.linux.lib.musl.general:9784 Archived-At: * Max Ruttenberg [2016-03-30 12:18:33 -0400]: > I've built musl on an Ubuntu VM (x86_64 is the architecture) and have > installed it to an install directory inside the downloaded clone. > > So the compiler is in: /path/to/musl/install/bin/musl-gcc > > The loader is in: /path/to/musl/install/lib/libc.so > > At the top level of libc-test I run a make like so: > > make CC=/path/to/musl/bin/musl-gcc RUN_WRAP=/path/to/musl/lib/libc.so > that's not the intended usage RUN_WRAP is for qemu or similar tools for running the binaries you can specify the libc.so by changing the dynamic-linker name (at least that's enough in case of musl) or installing the musl-gcc wrapper/musl based toolchain with different dynamic-linker name, e.g. make CC='/path/to/musl/bin/musl-gcc -Wl,-dynamic-linker=/path/to/musl/lib/libc.so' should work (not tested) > The tests run, I don't get the "no such file or directory" error. But for > some reason a bunch of tests fail that shouldn't according to the Libc-Test > wiki. What am I doing wrong? Are these tests dependent on system resources > that maybe I'm not providing e.g. enough memory? Do I need to run as a sudo > user as might be suggested by the "Operation not permitted" errors? > static linked binaries cannot be loaded by libc.so so all *-static.exe failed to run.