Re: Recommendation for Virtual Machine and Instructions to set it up?
On Thu, Dec 06, 2018 at 11:11:56AM -0500, firstname.lastname@example.org wrote:
> I'm involved with having some software written and then testing it.
> The software won't run on either my Wheezy or Jessie systems -- it appears to
> be an outdated libstdc++ that is the problem.
That seems to be rather peculiar. Is the software also built on the
wheezy or jessie system before attempting to run it, or is it built
elsewhere? What is the exact error output that you get? What is the
output of 'ldd /path/to/the/program'? Is it written in C++?
> We've tried a few different solutions, including trying to install updated
> libstdc++ library using dpkg -i
Wow. That is just asking for trouble. I strongly recommend against
> and having the package compiled statically
> (although, for some reason, the programmer couldn't get it completed static,
> it apparently still needs some share libraries).
That is not especially surprising. I have just today encountered an
open source project that I need to build from source that fails to build
if I try to static link it.
> Getting to the question:
> I suppose I could as some more questions related to that, but, for now, the
> next suggestion (aside from upgrading one of my machines to stretch (or
> whatever the current stable is) is to do something like create a virtual
> machine and install Ubuntu on it (because the programmer also uses Ubuntu and
> it works there for him) -- I suppose I might also (eventually) try stretch on
> the VM.
> I think I'd install the VM on my Jessie machine, as there is less data at risk
> there (and, of course, I need to backup that data before proceeding), but the
> question is:
> What would you recommend for the software to run a VM under Jessie (that would
> probably run Ubuntu), and can you recommend a fairly simple set of
> instructions to first set up the VM, and then at least begin the install
> process to that VM.
It seems like a chroot environment might be less work. Without knowing
precisely what resources the software needs, though I cannot be certain
if it is suitable. In any event, building a chroot environment is as
simple as installing debootstrap and then doing this:
sudo debootstrap unstable /path/to/chroot
After that, you can install your program under that directory and run it
sudo chroot /path/to/chroot /inside/chroot/path/program
Or, so work interactively in the chroot:
sudo chroot /path/to/chroot /bin/bash
The debootstrap utility knows about the Debian releases as well as the
Ubuntu releases and should be able to set up either. Though, you may
need to install an updated debootstrap for setting up chroots for the
latest Debian or Ubuntu releases.
Roberto C. Sánchez