Date: Thu, 21 Sep 2006 13:57:47 -0600 From: John E Hein <jhein@timing.com> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: freebsd-emulation@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: linux cross-development (was: Re: /dev/null: No such file or directory) Message-ID: <17682.61115.942535.166114@gromit.timing.com> In-Reply-To: <20060921075521.635qo889nkkg80cs@webmail.leidinger.net> References: <20060918230348.I1031@ganymede.hub.org> <20060919022530.GA44301@lor.one-eyed-alien.net> <20060919092117.8asq42ers44w4wgg@webmail.leidinger.net> <20060920014127.GA52449@xor.obsecurity.org> <20060920102554.mxditjplogkscw44@webmail.leidinger.net> <20060920182156.GA83026@xor.obsecurity.org> <20060920212442.41c9ed0f@Magellan.Leidinger.net> <17681.39712.119019.147240@gromit.timing.com> <20060921075521.635qo889nkkg80cs@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Leidinger wrote at 07:55 +0200 on Sep 21, 2006: > Quoting John E Hein <jhein@timing.com> (from Wed, 20 Sep 2006 13:48:48 -0600): > > Alexander Leidinger wrote at 21:24 +0200 on Sep 20, 2006: > > > Any ideas how to provide a chroot while not losing the fallthrough if > > > not chrooted (and we try to identify other files/dirs where we want a > > > fallthrough)? > > > > That smells a little like unionfs. > > Feel free to provide a description how to achieve this. I don't see > it at first look. I haven't thought about it. It just sounded a bit like unionfs. > And I don't like to mount stuff at installation time or to request > to mount something to get it working. I agree. > > From a system building perspective, it seems difficult to build a > > system in an automated way (as in a product) that needs to build apps > > compiled for linux. > > > > We build packages in a FreeBSD chroot and pkg_add -p them into an > > image hierarchy (which is then copied to the target media, typically a > > Compact Flash). > > > > So, if we wanted to deploy a system that has linux_base and some > > linux-compiled apps, we'd have to build the linux_base .tgz package in > > our build chroot, pkg_delete it, then install linux_dist in order to > > compile linux apps (there are some closed linux libs we need to link > > You don't need to delete the linux_base. linux_dist-gentoo-stage3 > installs into /usr/local/gentoo-stage3. As long as you do a chroot > into the linux directory, you will not have any problem. If you don't > do a chroot, you have to be careful to not pick up FreeBSD stuff. This > may or may not work. If you are very careful, you can do a > cross-build, but if you do real cross-development, you should really > do a chroot (else you have to verify in the worst case for every bug > that no FreeBSD stuff is picked up instead). Okay, I see that linux_base & linux_dist can co-exist. But I still see some problems... I'd have to change our build to get the source code into the gentoo chroot. Plus right now, the app is built as a FreeBSD port, so I'd have to get the FreeBSD ports infrastructure (and make(1)) working under the gentoo chroot, too. That could be a lot of work. Also, if I build in the gentoo chroot, but deploy the app to be run under linux_base, I suspect there may be library conflicts (this is not unlike the problems that have been mentioned for linux_devtools).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17682.61115.942535.166114>