[email protected] said: > One string we could pull from in the future is the fact that we're > crosscompiling, and the build system doesn't know how to run the > resulting binary. So we could pseudo-link the target, and then have > rumprun actually link it (and cache the result). That approach > should also solve cases where we'd want to crunch multiple binaries > into a single image. I'm sure there are examples and experiences of > this type of approach floating about, just need to survey them for > the drawbacks.
How would such pseudo-linking work? Please point me to the examples you mention, so that I can get an idea of what would be required. We can't use "ld -r" as a pseduo-link step, since that just treats undefined symbols as "will be resolved later".
