Re: [Mingw-cross-env-list] Re: binutils: bfd.h is missing

[Tony Theodore]

On 13 October 2010 21:08, Martin Gerhardy <address@hidden> wrote:
>> The file bfd.h is not installed with binutils. Is there any reason for
>> this? Or just a bug?
>
> Attached is a patch the tries to fix this - the remaining problem is
> that installation directory is wrong:
>
> ./powerpc64-unknown-linux-gnu/i686-pc-mingw32/include/bfdlink.h
> ./powerpc64-unknown-linux-gnu/i686-pc-mingw32/include/bfd.h
> ./powerpc64-unknown-linux-gnu/i686-pc-mingw32/lib/libbfd.a
> ./powerpc64-unknown-linux-gnu/i686-pc-mingw32/lib/libbfd.la
>
> it should of course be
>
> ./i686-pc-mingw32/include/*

Or just usr/include - don't forget that this is a native build, not a
cross build. Do you have a powerpc64* directory somewhere under your
mingw-cross-env?

> But i still don't know whether there is a reason this is not installed
> by default and couldn't find references or anything else on the web
> about this.

I'm guessing that you would only need to install the headers and libs
if you were developing something like binutils itself or other low
level compiling/assembly/linking programs. In that case, you'd
probably do either a fully native build, or a second level build where
the final output is actually a binutils to be executed on the new
host. Neither of those scenarios are covered by mingw-cross-env at the
moment - the first never really would be (package managers do that),
and the second seems like it would be bootstrapping an "msys-like"
environment (interesting but very time-consuming).

What exactly are you trying to do, and why are the "missing" headers a problem?

Cheers,

Tony