From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/10661 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Unable to build with --enable-shared Date: Sun, 23 Oct 2016 12:17:08 -0400 Message-ID: <20161023161708.GB19318@brightrain.aerifal.cx> References: <20161022215829.GA5749@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1477239465 17058 195.159.176.226 (23 Oct 2016 16:17:45 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 23 Oct 2016 16:17:45 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-10674-gllmg-musl=m.gmane.org@lists.openwall.com Sun Oct 23 18:17:41 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1byLSj-0002Kw-8D for gllmg-musl@m.gmane.org; Sun, 23 Oct 2016 18:17:29 +0200 Original-Received: (qmail 30278 invoked by uid 550); 23 Oct 2016 16:17:28 -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 30257 invoked from network); 23 Oct 2016 16:17:27 -0000 Content-Disposition: inline In-Reply-To: Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:10661 Archived-At: On Sun, Oct 23, 2016 at 02:22:28AM +0200, Samuel Sadok wrote: > 2016-10-22 23:58 GMT+02:00 Szabolcs Nagy : > > * Samuel Sadok [2016-10-22 22:37:46 +0200]: > >> I am unable to build musl with --enable-shared. Multiple issues in > >> unrelated projects (e.g. here: https://bugs.swift.org/browse/SR-1023) > >> suggest that the culprit is a change in behaviour between binutils > >> 2.25 and 2.26. > >> > > > > that bug is different, that's about object symbols > > > > (swift seems to misuse protected visibility objects, > > and instead of fixing the problem they switched to the > > gold linker which does not yet have the bfd linker fix, > > such incompetence is frustrating.. however the issue > > does not affect musl: we don't mark objects protected > > to avoid issues with broken toolchains.) > > That's precisely why I'm trying to get away from Apple. > > > > >> $ make > >> [...] > >> x86_64-pc-linux-gnu-gcc -D_XOPEN_SOURCE=700 -I./arch/x86_64 > >> -I./arch/generic -Iobj/src/internal -I./src/internal -Iobj/include > >> -I./include -include vis.h -B/usr/local/bin/x86_64-pc-linux-gnu- > >> -fPIC -c -o obj/src/process/posix_spawn.lo src/process/posix_spawn.c > > > > some flags are missing here.. e.g. freestanding flags > > Thanks for the pointer, that turned out to be the problem. > > I should mention that I am cross-compiling from macOS. Since I had a > Linux VM flying around, I tried to build musl there (success) and > compared the logs. > Looking at config.mak, there apparently was a serious misconfiguration: > > config.mak on the cross-build system (macOS): > > CFLAGS_AUTO = -include vis.h > CFLAGS_C99FSE = > CFLAGS_MEMOPS = > CFLAGS_NOSSP = > LDFLAGS_AUTO = > LIBCC = This probably indicates something is wrong with your cross toolchain; even if you manually fix config.mak, I would be concerned that something might have been built wrong. What cross toolchain are you using and how was it setup? How did you invoke configure? Rich