Will CLFS resolve my issue below
 

Hi,

Sorry, if this question has been repeatedly asked and answered. I also tried searching, but to my search i was unable to figure out an answer.

My Objective:
-------------

To have a separate folder of cross-tools in my development machine(amd64) for GCC, glibc(? - though i prefer this compared to uClibc because my development is mainly in c++ and i don't know if uClibc or newlib would go well with libstdc++) and libstdc++(i really want to use the STLs). So these 3 i need it in a separate folders for x86 and arm architectures

My Question is
---------------
1. So where should i start?

2. Will it suffice if i just use CLFS guide to start building on my development machine.

3. another weird question, though it is possible i suppose
can i crosscompile for the same architecture as my development machine(x86_64) and keep the binaries in a separate folder. Though this sounds weird, the reason i want to do this is that, i could freeze the versions of kernel, libraries and gcc and prepare to build system to always point to the directories when linking the libraries. This way to move the development system to a different computer all i would have to do is just to copy the tools folder to the new pc.

Yes you can, but it will a bit different, to use CLFS as a cross-compiler you would have to use a fake root, and then just chroot into it when you wish to use it, because unless your plan is to relocate every default directory for GCC, libc and all the rest of the entire cross tool chain this is the only way i can think of to make that work.

What do you mean by freezing though? essentially the entire fake root will be frozen unless you make changes to it as root (when you chroot into it)

Hmmm, let me start with it then, and will come back here again when i start facing issues, maybe i would read the readme wiki thoroughly first to get the understanding...

By freezing, i meant i would freeze the versions of gcc, glibc, kernel headers etc., in my tools directory, rather if i use my same dev machine's headers and glibc, with every update i do, there is a possibility that i may by mistake update the libraries etc., instead if i used a seperate folder, i could manually control the versions i use there.

i felt that would be nice.