Re: Install $prefix and $prefix/$target Directory Clarifications

[Dan <dan dot gisselquist at gmail dot com>]

Kyle,
I've been working on my own cross utilities for some time.  I currently
maintain them as a patch to the binutils repository.  You might find
that a patch is useful to figure out what components you will need to
work on to get your cross tool chain up and running.
In my case, you can find the patch here:
https://github.com/ZipCPU/zipcpu/blob/master/sw/gas-zippatch.patch
It currently patches against binutils 2.27, but I wouldn't expect any
amazing issues pushing this forward.
If you examine the script that I have that calls configure,
https://github.com/ZipCPU/zipcpu/blob/master/sw/gas-script.sh

you can see how I handled some of the path issues.
Not sure if this will help or not, but I thought I might offer it in
case.
Dan
On Thu, 2018-03-08 at 21:08 -0500, Kyle Burge wrote:
> Hello,
> 
> I apologize if this is a duplicate thread but I've searched high and
> low
> through the mailing lists for information on this subject with no
> success.
> I'm currently trying to build a cross compiler and toolchain and I've
> gotten everything almost worked out. The only issue now is that the
> packages I built for the target system (with my cross compiler) do
> not seem
> to be receiving the correct paths for includes, the dynamic linker,
> libraries, etc. Even if I check the paths and they seem correct, I'll
> still
> get dynamic linker or shared library errors related errors. Or when I
> try
> to build the target coreutils, the build fails because of an
> incorrect
> MB_LEN_MAX (multi-byte character size) definition in header files.
> This
> surely has something to do with the compiler finding the wrong
> limits.h
> files or the files were built incorrectly in the first place.
> Getting to the point then, I feel like I have some fundamental
> misunderstandings with the cross compiler directories relating to
> prefix
> flags, with-local-prefix flags, sysroot/build-sysroot flags, etc.
> Why exactly does binutils and GCC install one set of tools in the
> $prefix
> directory and another in the $prefix/$target directory? I seem to
> need both
> sets of tools.
> I've been trying to install my target packages in the
> $prefix/$target, is
> this correct?
> How does sysroot flags relate to all of this and when exactly should
> I use
> them? When the system libraries and headers are in a different place
> than
> $prefix right?
> But now doesn't the -with-local-prefix flag do something similar as
> per:
> https://gcc.gnu.org/install/configure.html.
> If you guys could just give me a few pointers that would be
> fantastic.
> Thanks!
> 
> Kyle