On Tue, Aug 13, 2024 at 01:35:03PM +0200, julien.pu...@gmail.com wrote: > > > And of course, this is where I came to my wits' end: I can compile > > > the > > > new elpi successfully... but I have no way to install this new elpi > > > binary packages in the schroot to test it against different coq- > > > elpi! > > > > Yes, the usual recommendations are "unpack and try pointing to it via > > stuff like LD_LIBRARY_PATH, hopefully such stuff exists for your > > case". > > It doesn't: it's a mix of languages. C, OCaml, elpi and Coq I would > say. > > > Consider using local qemu chroots instead. > > > > I'd like a one-page easy-to-use tutorial on this.
It's like normal sbuild but pass --arch=foo to sbuild-createchroot and to sbuild. You'll need qemu-user-static installed. That's all IIRC. > > > dd-cross-schroot-cmd -s $sessionid -a $targetarch apt-get install > > > ./*foo*_3.14-159_$targetarch.deb > > > > This still runs random code as root. > > > > I don't think running random code as root in a virtual environment I'm > going to delete before the end of the day is a security issue. Well, that's the only reason I can think for not being able to run root commands in porterbox chroots directly. -- WBR, wRAR
signature.asc
Description: PGP signature
