From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9682 Path: news.gmane.org!not-for-mail From: Michael McConville Newsgroups: gmane.linux.lib.musl.general Subject: Re: Add support for amd64 target Date: Fri, 18 Mar 2016 00:02:11 -0400 Message-ID: <20160318040211.GA80609@thinkpad.swarthmore.edu> References: <20160318023341.GB71208@thinkpad.swarthmore.edu> <20160318034622.GM21636@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1458273754 14440 80.91.229.3 (18 Mar 2016 04:02:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 18 Mar 2016 04:02:34 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9695-gllmg-musl=m.gmane.org@lists.openwall.com Fri Mar 18 05:02:32 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 1aglcO-0000yO-3b for gllmg-musl@m.gmane.org; Fri, 18 Mar 2016 05:02:32 +0100 Original-Received: (qmail 32560 invoked by uid 550); 18 Mar 2016 04:02:30 -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 32542 invoked from network); 18 Mar 2016 04:02:30 -0000 X-Virus-Scanned: amavisd-new at kolabnow.com X-Spam-Flag: NO X-Spam-Score: -2.9 X-Spam-Level: X-Spam-Status: No, score=-2.9 tagged_above=-10 required=6.31 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, FREEMAIL_FROM=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham Content-Disposition: inline In-Reply-To: <20160318034622.GM21636@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:9682 Archived-At: Rich Felker wrote: > On Thu, Mar 17, 2016 at 10:33:41PM -0400, Michael McConville wrote: > > For what it's worth, the build then survives until linking. I > > haven't had a chance to diagnose that problem yet. > > What are the linker errors you hit? It's not surprising that compiling > would work since no files external to the musl source tree are > accessed during compiling, but linking could bring in lots of issues, > and runtime even more. To clarify: I thought the platform-specific bits would cause more problems at runtime than at compile-time, but the more I think about that the less it makes sense. You're definitely right - getting a reliably working port will take a good deal of work (hence it being offered as a three-month project). It's just nice to know that the actual C code is reasonably portable.