From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9688 Path: news.gmane.org!not-for-mail From: Isaac Dunham Newsgroups: gmane.linux.lib.musl.general Subject: Re: Add support for amd64 target Date: Thu, 17 Mar 2016 22:08:25 -0700 Message-ID: <20160318050823.GB8521@newbook> References: <20160318023341.GB71208@thinkpad.swarthmore.edu> <20160318034622.GM21636@brightrain.aerifal.cx> <20160318035447.GB19612@thinkpad.swarthmore.edu> 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 1458277735 2699 80.91.229.3 (18 Mar 2016 05:08:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 18 Mar 2016 05:08:55 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9701-gllmg-musl=m.gmane.org@lists.openwall.com Fri Mar 18 06:08:43 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 1agmeQ-0002ly-QZ for gllmg-musl@m.gmane.org; Fri, 18 Mar 2016 06:08:42 +0100 Original-Received: (qmail 13505 invoked by uid 550); 18 Mar 2016 05:08:40 -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 13484 invoked from network); 18 Mar 2016 05:08:40 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=kOCvHHOnlzVKdT/CLPuv56XOzqPjuHgnf3JU0zhh7/4=; b=bSCzwLSjcapl5CeYpcZr1W3PPbxJyRX+utjV2xzNUOgAwk9FNNtHLhe09hxTYmq22S JEzemzj5E1wYJA4eARCx3ve1UL++TCciL5Ra58vXhPyQhp/e1gqE6RCeKbMM8ioB3jze rmAShIKmADoY0R5560lP0I6I/gWNyBGsX2wbo2XuRp4J585W5j9lvhCv7RnM3nqR9Qfh fmd4e3wCnJxu3w9Dihxz4fNXXWZ108XH8quoPJVJ3KsuEL1h+a3J8OAu+QCmC6uOfa+W yNIdT0gl/M/73t+oEq5kMeun9lt1Ok51gj2NzBoy/bEcxsjLDulxGC1rDRQrKRsUOAJH D/gQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=kOCvHHOnlzVKdT/CLPuv56XOzqPjuHgnf3JU0zhh7/4=; b=WF4iPsMMLI49iH7PJ/M55NvHEv1MwZkCu9UH5uwwcnzYCwP4UXbLJyOqpJmPWKKyN6 spgIY7h9ne3DfphXNX1xHNFjtCb/udiXyI/Fz8KkgvlNixwy0RRM2jdguNyTSPyCoiNT 0QjO69OLiVYuNJHOZ8Hzrnt+rtlVSTfBC+EbfxzFksZHZfXFFDldglPJYUCfRqkN/xXs ZPVVNaIsfxWBGvsz2YOBNwDpIfcAyeDbYMojsJbyTbuEqaKfS9Tu3aK8HFbShR90+eGu uADp1LCu8W2zL+JHIT1l7ja+hyqGZAl/QQ0g8HcU4BPxLNBKxGgxoRAowz9I8op9N2RP h49A== X-Gm-Message-State: AD7BkJJi+PLNnCdyQNwfUVlgxMRdLslmfLdyb1ZzHAh11X1ZMqOQZO58v+egmCkqibn++A== X-Received: by 10.98.13.88 with SMTP id v85mr20536434pfi.150.1458277708090; Thu, 17 Mar 2016 22:08:28 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20160318035447.GB19612@thinkpad.swarthmore.edu> User-Agent: Mutt/1.5.24 (2015-08-30) Xref: news.gmane.org gmane.linux.lib.musl.general:9688 Archived-At: On Thu, Mar 17, 2016 at 11:54:47PM -0400, Michael McConville wrote: > Rich Felker wrote: > > On Thu, Mar 17, 2016 at 10:33:41PM -0400, Michael McConville wrote: > > > AMD64 and x86-64 are effectively interchangeable terms. BSDs use the > > > prior while Linux uses the latter. The below patch therefore fixes > > > configure on OpenBSD. > > > > I'm not opposed to adding this if you think it will help, but I'm > > skeptical of whether a toolchain targeting OpenBSD can produce a > > working musl build anyway. Are you trying to get something that runs > > on OpenBSD or use the OpenBSD compiler as a makeshift cross compiler > > to get a normal Linux build? > > FreeBSD and RISC-V (one an OS and the other an architecture, of course) > both have Google Summer of Code projects for porting musl. This > interests me, and because I'm on OpenBSD developer I thought I'd give it > a try on OpenBSD. > > Whether or not I do either of the GSoC projects or follow through with > an OpenBSD port, it's likely that someone will take up the FreeBSD > project. In that case, this patch will have to be applied. > > I'm hopeful that BSD ports won't be invasive, considering how long the > unpatched (ignoring the trivial configure patch) build ran. > > > > 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. > > On what seems to be the final link command (judged from the number of > object files involved), I get this: > > > obj/src/aio/aio.lo: In function `aio_cancel64': > > aio.c:(.text.aio_cancel+0x19): undefined reference to `__guard_local' > > /usr/bin/ld: obj/src/aio/aio.lo: relocation R_X86_64_PC32 against `__guard_local' can not be used when making a shared object; recompile with -fPIC > > /usr/bin/ld: final link failed: Bad value > > collect2: ld returned 1 exit status > > Makefile:163: recipe for target 'lib/libc.so' failed > > gmake: *** [lib/libc.so] Error 1 > > We have some unique PIE features on by default, so this doesn't surprise > me. This means that you've got OpenBSD SSP turned on. It's no surprise that this doesn't work; for an overview of some trouble spots, I'll mention this link: http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20130603/176378.html Try turning it off (-fno-stack-protector or equivalent) for starters. Long-term, a proper port might require patching musl to support OpenBSD SSP. By the way, is this the stock OpenBSD GCC 4.2? HTH, Isaac Dunham