mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: binutils odd compile behavior
Date: Mon, 24 Nov 2014 18:48:31 -0500	[thread overview]
Message-ID: <20141124234831.GO29621@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAA7aPHivn+0bDe_51CphO0HuHdA4SSh+KNA4SKp8ENZ4i1fD0Q@mail.gmail.com>

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


  reply	other threads:[~2014-11-24 23:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 20:18 stephen Turner
2014-11-24 23:48 ` Rich Felker [this message]
2014-11-25  0:26   ` stephen Turner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141124234831.GO29621@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).