Thanks Tristan, You are too kind! I had been lurking on the list with my main personal address; I set up gmail to get more active. My mistake not to have thought it through, and I am sorry to have caused you some work.
Anyway, the build had gone fine. It was the extra commented 'make install' I was using to validate the build. So, I've attached a working Vagrantfile, building into ubuntu/32 since that's Vagrant's site demo instance and should be well supported. What's nice is that the source machine, install steps, build steps are all included in one text file of about twenty lines, linking into existing standards (like build_gcc.sh). To use (*): Create a new folder and move into it. Copy Vagrantfile to this folder (keep the name). Run 'vagrant up'. Wait a few hours.. To check: Run 'vagrant ssh', then 'cd Projects/gcc4.8.2/build/gcc' and './ghdl -v'.
Vagrantfile
Description: Binary data
A lot more complexity is possible, including the use of chef/puppet primitives, auto-test etc. Also, it's best if the Vagrantfile definition is checked in with the source. My task is to learn the code but I'm very happy to get involved in these aspects too. Best regards, Stephen (*) You'll need a working Oracle Virtual Box + Vagrant setup - both of these are free of charge and run on many operating systems.
_______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
