binutils odd compile behavior

binutils odd compile behavior

[stephen Turner]

[-- 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 --]

Re: binutils odd compile behavior

[Rich Felker]

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

Re: binutils odd compile behavior

[stephen Turner]

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

On Nov 24, 2014 6:48 PM, "Rich Felker" <dalias@libc.org> wrote:
>
> 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?
>

At present I havent recievied even a "its your fault" for the email on
headers (which was my fault anyways) or several others, however fwiw I have
moved past those issues.

Everyone I think was overlooking it (understandably so) because they knew
it was a id10t error and were focused on the atomics work coming through.

> > 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

I just found out about the musl out of tree issue from another member. Not
sure why I would see the same behavior from binutils however. Per the
advice of the other list member im cleaning up my build process by not
specifying the include and lib dir's to see if that in some way helps with
binutils.

Thanks,
Stephen

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