AMDG Robert P. J. Day wrote:
LTIB is a packaging system used to build cross-compiled root filesystems (a la buildroot, sort of like that). what makes LTIB a bit different is that the entire build runs inside a "spoofed" environment, where normal executable names like "gcc" and "ld" and so on are aliased to their cross-compile counterparts. in other words, packages are built "normally", allegedly never realizing that their invocations of the compiler tools are actually being redirected to their cross-compiler equivalents.
most of the time, this works just fine, but it runs into problems if part of the build *needs* to invoke the native tools, and i think that's what's happening when you try to "make install" after the build.
Can you build bjam for the host system first?
as i read it, "make install" requires jam, correct, which it would find in tools/jam/src/bootstrap/jam0? and this executable does in fact exist, but it's the *cross-compiled* version, and therefore of no use on the build system.
This isn't quite true, but the result is the same. build.sh first builds jam0 which it then uses to build bjam. The tool used by make install is bjam. In Christ, Steven Watanabe