From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9500 Path: news.gmane.org!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: Problem with musl-gcc script. Is it bad installation? Date: Sun, 6 Mar 2016 02:14:00 +0100 Message-ID: <20160306011400.GR29662@port70.net> References: <20160306002823.09d603d7c3d8fe4b0f4b15c1@asm32.info> <20160306003609.GO9349@brightrain.aerifal.cx> <20160306030230.cedf8eded77c37ec1d450f3c@asm32.info> <20160306010907.GQ29662@port70.net> 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 1457226867 22346 80.91.229.3 (6 Mar 2016 01:14:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 6 Mar 2016 01:14:27 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9513-gllmg-musl=m.gmane.org@lists.openwall.com Sun Mar 06 02:14:18 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 1acNGw-0006Zi-Md for gllmg-musl@m.gmane.org; Sun, 06 Mar 2016 02:14:14 +0100 Original-Received: (qmail 17919 invoked by uid 550); 6 Mar 2016 01:14:12 -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 17889 invoked from network); 6 Mar 2016 01:14:11 -0000 Mail-Followup-To: musl@lists.openwall.com Content-Disposition: inline In-Reply-To: <20160306010907.GQ29662@port70.net> User-Agent: Mutt/1.5.24 (2015-08-30) Xref: news.gmane.org gmane.linux.lib.musl.general:9500 Archived-At: * Szabolcs Nagy [2016-03-06 02:09:07 +0100]: > * John Found [2016-03-06 03:02:30 +0200]: > > > On Sat, 5 Mar 2016 19:36:09 -0500 > > Rich Felker wrote: > > > > > The musl-gcc script is limited in its usefulness, and was not really > > > designed/tested for repurposing an existing x86_64 gcc as an i386-musl > > > one. You should be able to make it work though by editing the musl-gcc > > > script to remove the double quotes around "${REALGCC:-...}". If that > > > works for you, this is possibly a change we should make upstream. > > > > > > Rich > > > > After the suggested change, I can start musl-gcc and it even accepts some commands as --help > > But trying to use it with ./configure script again fails with: > > > > checking for gcc... musl-gcc > > checking whether the C compiler works... no > > configure: error: in `/work/cwork/SQLite/sqlite-autoconf-3110100': > > configure: error: C compiler cannot create executables > > See `config.log' for more details > > > > In the config.log I found the following: > > > > configure:3234: musl-gcc conftest.c >&5 > > /usr/bin/ld: skipping incompatible /usr/local/musl/lib/libc.so when searching for -lc > > /usr/bin/ld: skipping incompatible /usr/local/musl/lib/libc.a when searching for -lc > > /usr/bin/ld: cannot find -lc > > collect2: error: ld returned 1 exit status > > your gcc toolchain does not support -m32 > because it's missing i386 gcc runtime libraries. > > install the appropriate i386 libgcc package or > get a proper i386 toolchain. > on a second thought that would prevent the musl build too, i think musl-gcc does not pass the -Wl,-melf_i386 to the linker > > configure:3238: $? = 1 > > configure:3276: result: no > > configure: failed program was: > > | /* confdefs.h */ > > | #define PACKAGE_NAME "sqlite" > > | #define PACKAGE_TARNAME "sqlite" > > | #define PACKAGE_VERSION "3.11.1" > > | #define PACKAGE_STRING "sqlite 3.11.1" > > | #define PACKAGE_BUGREPORT "http://www.sqlite.org" > > | #define PACKAGE_URL "" > > | #define PACKAGE "sqlite" > > | #define VERSION "3.11.1" > > | /* end confdefs.h. */ > > | > > | int > > | main () > > | { > > | > > | ; > > | return 0; > > | } > > > > > > Regards > > -- > > http://fresh.flatassembler.net > > http://asm32.info > > John Found