From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6614 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: binutils odd compile behavior Date: Mon, 24 Nov 2014 18:48:31 -0500 Message-ID: <20141124234831.GO29621@brightrain.aerifal.cx> 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 1416872932 28783 80.91.229.3 (24 Nov 2014 23:48:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 24 Nov 2014 23:48:52 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6627-gllmg-musl=m.gmane.org@lists.openwall.com Tue Nov 25 00:48:46 2014 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 1Xt3N7-0007Oa-NZ for gllmg-musl@m.gmane.org; Tue, 25 Nov 2014 00:48:45 +0100 Original-Received: (qmail 13852 invoked by uid 550); 24 Nov 2014 23:48:44 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 13840 invoked from network); 24 Nov 2014 23:48:43 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:6614 Archived-At: On Mon, Nov 24, 2014 at 03:18:42PM -0500, stephen Turner wrote: > I dont know if im being filtered, ignored, or overlooked for the recent > work on atomics but i found an oddity and if its a concern to anyone let me > know and i will get you the info you want. Which particular message are you waiting for a reasponse to? > I built a chroot environment using busybox, binutils 2.24 and gcc 4.2.1. > While in the chroot i could not compile binutils. > > I keep a seperate code directory and build directory. When i build binutils > outside of the code directory it normally builds fine until i enter the > newly built musl chroot and then it starts to have errors with bfd. If > however i go into the binutils directory and compile (against > recommendations on lfs etc) it works fine. Without actually describing the errors you're getting and the procedure that led to them, there's not much hope to guess what the cause is. > I have the same issue when building musl only it works that way on debian > or my musl system. If i compile musl in a seperate build folder it errors > out but running the build from within the source folder works fine. musl does not support out-of-tree builds. That should probably be documented explicitly somewhere, but I don't think it is. Sorry. We'd like to add support for this at some point but there were buggy corner cases when nsz tried, and the work on this has been put aside for the time being. So for now you need to build it in-tree. You can duplicate your tree before building if you want to keep a clean tree, but "make distclean" should return your build tree to a clean state too. Rich