From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6613 Path: news.gmane.org!not-for-mail From: stephen Turner Newsgroups: gmane.linux.lib.musl.general Subject: binutils odd compile behavior Date: Mon, 24 Nov 2014 15:18:42 -0500 Message-ID: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=bcaec51b180537c6cb0508a08059 X-Trace: ger.gmane.org 1416860343 10091 80.91.229.3 (24 Nov 2014 20:19:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 24 Nov 2014 20:19:03 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6626-gllmg-musl=m.gmane.org@lists.openwall.com Mon Nov 24 21:18:56 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 1Xt064-0004ha-4Z for gllmg-musl@m.gmane.org; Mon, 24 Nov 2014 21:18:56 +0100 Original-Received: (qmail 1733 invoked by uid 550); 24 Nov 2014 20:18:54 -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 1724 invoked from network); 24 Nov 2014 20:18:54 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=q8vFrRqimMz2gyfXkCyObGeM3VLhkB6rQ5ciJty8q4s=; b=nkLMfB4ZO01Ab/xhoVN7u7WgXUnmCXo7a5wegsr3l0tzukZrsPO2NCvg2CZWS99O5T Idaxbf4eUnRTFeU9o6PdsH9E63QmHMuVVWs/o8D8/U2/jWIt75uvjJXWN2pubKhoA+AT s2bqDZBjhrcjbndIc78CO36D0qSxe6qS/R813WOJpkwxgGnQCHAKeNWFEcULwJALmuMx RhI439Troc/JEi27cnO2VE0mOHWH1Efts3EvuSKNZegZqkYaterOWtLKsxi9t39xQbum 8KVhnaMElUFfCX0BJ53YCJTQt334dR8bwaKVVMFa/fB5JOTRlsvsDS0ZNMTA3t2OdVMK mQvw== X-Received: by 10.52.172.167 with SMTP id bd7mr10879387vdc.30.1416860322472; Mon, 24 Nov 2014 12:18:42 -0800 (PST) Xref: news.gmane.org gmane.linux.lib.musl.general:6613 Archived-At: --bcaec51b180537c6cb0508a08059 Content-Type: text/plain; charset=UTF-8 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. 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. 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. I cant say if this is an environmental issue on my musl system or a code issue with musl or binutils but Its something i have definately had to work through. example: I untar musl-1.1.5 to /home/musl I create dir /home/build running ../musl/configure from /home/build errors before completion. thanks stephen --bcaec51b180537c6cb0508a08059 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I dont know if im being filtered, ignored, or overlooked f= or 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.

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 binutil= s outside of the code directory it normally builds fine until i enter the n= ewly built musl chroot and then it starts to have errors with bfd. If howev= er i go into the binutils directory and compile (against recommendations on= lfs etc) it works fine.

I have the same issue whe= n building musl only it works that way on debian or my musl system. If i co= mpile musl in a seperate build folder it errors out but running the build f= rom within the source folder works fine.

I cant sa= y if this is an environmental issue on my musl system or a code issue with = musl or binutils but Its something i have definately had to work through.

example:
I untar musl-1.1.5 to /home/musl=
I create dir /home/build
running ../musl/configure fro= m /home/build errors before completion.

thanks
stephen
--bcaec51b180537c6cb0508a08059--