virtual machines
Jun. 26th, 2012 07:00 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
izardI just needed to compile two big open source packages for a 32 bit embedded target. I wanted to compile them on my dual socket SNB workstation as it is the fastest I have. It runs 64 bit open SuSe, so for cross-compilation I installed gcc-32, all 32 bit dev utils, binutils-32, ran linux32, made all necessary changes to config and make files. Still one of the linking targets failed to build.
Few years ago, I would either continued digging down this SCM mess (the most dreadful task in our trade, the stuff I hate most), or moved to a host which runs i386 Linux. (I have one but not as powerful). Now thanks to VT-x, VT-d and VT-c support by mainstream hypervisors I will just install one tomorrow morning, get an image of 32 bit ubuntu running, configure it as dev host and compile my stuff. That will go naturally, easily and I think nearly as fast as native.
Few years ago, I would either continued digging down this SCM mess (the most dreadful task in our trade, the stuff I hate most), or moved to a host which runs i386 Linux. (I have one but not as powerful). Now thanks to VT-x, VT-d and VT-c support by mainstream hypervisors I will just install one tomorrow morning, get an image of 32 bit ubuntu running, configure it as dev host and compile my stuff. That will go naturally, easily and I think nearly as fast as native.
