[libre-riscv-dev] [Bug 178] first coriolis2 tutorial, workflow and "test project" page

bugzilla-daemon at libre-riscv.org bugzilla-daemon at libre-riscv.org
Tue Mar 10 11:51:23 GMT 2020


--- Comment #197 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Jock Tanner from comment #196)
> (In reply to Luke Kenneth Casson Leighton from comment #192)
> > three options, very simple.
> > 
> These are the options of accessing program text. What I'd like to have is an
> option of accessing the interpreter.

ahh ok.  *thinks*.

you could try to "virtualenv" the version of python inside the chroot to
*outside* the chroot by executing it from outside, with suitable
LD_LIBRARY_PATHs and PYTHON_PATHs etc.  those will simply be extended
"/home/chroot/coriolis/usr/lib/python3.7/dist-packages" etc. although that's
more likely to work if you're using debian-on-debian.

all quite a lot of hassle that is not a good idea even if using docckkkaa
because we need to *not* install arbitrary software inside the chroot, for risk
that it "upgrades" or installs additional software dependencies in a way that
adversely affects builds.

one other possible route would be pyro.  (python remote-objects).  it works. 
it's pretty minimalist.  you *might* get away with it: just try not to abuse
it, and bear in mind that when it comes to final production builds, we *really*
cannot have anything other than the absolute minimum in the chroot.

yesyes i know i said "no extra software" then suggested installing pyro.  if
i'm installing vim and editing inside the chroot, you can sneak pyro in :)

You are receiving this mail because:
You are on the CC list for the bug.

More information about the libre-riscv-dev mailing list