mailing list of musl libc
 help / color / mirror / code / Atom feed
From: stephen Turner <stephen.n.turner@gmail.com>
To: musl@lists.openwall.com
Subject: binutils odd compile behavior
Date: Mon, 24 Nov 2014 15:18:42 -0500	[thread overview]
Message-ID: <CAA7aPHivn+0bDe_51CphO0HuHdA4SSh+KNA4SKp8ENZ4i1fD0Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1376 bytes --]

             reply	other threads:[~2014-11-24 20:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 20:18 stephen Turner [this message]
2014-11-24 23:48 ` Rich Felker
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=CAA7aPHivn+0bDe_51CphO0HuHdA4SSh+KNA4SKp8ENZ4i1fD0Q@mail.gmail.com \
    --to=stephen.n.turner@gmail.com \
    --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).