Answer the question
In order to leave comments, you need to log in
What is the right way to build a gcc toolchain (and how to isolate it) for the x86_64 target system?
These toolchain descriptions are killing me.
I'm just completely confused with them: cross-native, cross, cross-candian.
Here is my vision of how it should be:
I have 2 hosts. First, I use gcc from the system to build gcc5.2 (locally prefixed simply) to build everything else. After that, with its help, I need to collect the GCC toolchain (it needs binutils, headers, etc.) and isolate it. thus we will achieve just an isolated toolchain. with its help, in theory, I can assemble it by passing a pack of software flags for host2. I also want a cross compiler already (also an isolated toolchain) in which there will already be all the target options. those. I give him -native, and he gives me ready-made software. and I need a third toolchain (not assembly, but isolated and assembled for the target). in which there will be everything you need stupidly to run the software (i.e. I don’t need to build it there, but I need to run the binaries. In fact, this is a cropped build_toolchain)
Where am I wrong, wrong and how do I understand it all (
Answer the question
In order to leave comments, you need to log in
chroot or a virtual machine as already a solution to the question "well, maybe in the forehead", but in general docker will help you, it was invented for such tasks :)
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question