Messages in this thread | | | Subject | Re: chroot(2) and bind mounts as non-root | From | Colin Walters <> | Date | Thu, 08 Dec 2011 13:26:40 -0500 |
| |
On Thu, 2011-12-08 at 13:14 -0500, John Stoffel wrote:
> Or is it because you're trying to edit on one OS, such a fedora 14, > then build and debug inside an Debian 5.0 setup? But without running > a completely seperate system, but just doing a chroot into a new > filesystem tree?
Yes, something like that; basically it's about ensuring that the libfoo we're building binaries against is /home/walters/build/libfoo.so and not /usr/lib/libfoo.so.
I'm actually intending for the core build system of my OS to work in *both* cross and native compilation. That means it's important to keep them as close as possible.
What you were talking about above (i.e. "just don't chroot") is what http://buildroot.net does (and others, I also semi-maintain GNOME's jhbuild). It works if you're very careful in your build scripts, know and carefully propagate the large set of magic environment variables, etc., then yes, you can do it.
But chroot is just so nice a hammer for this nail.
| |