The Workbench 2016-09
What is on my workbench these days?
I've started on SFEgcc 5.4.0. The main goal for the SFEgcc implementaion is again loading the gcc runtime from the private directories first. As well we disable "LAZY_LOAD" to avoid binding C++ calls to /usr/lib/libc.so in accident (causing core dumps with C++ code as the are to be bound to libstdc++.so.6).
The 5.x series will have a new layout for directories. It only contains the major version number in the path (5 instead 5.4). Another change is a new prefix directory /usr/gcc-sfe. The reason for this is, that with OSDistros providing current gcc versions themselves and using the same directory layout /usr/gcc, we get in a few cases into file conflicts if the user installs the compiler from OSdistro. Example new path will be /usr/gcc-sfe/5 or in case it will be implemted for 4.8 / 4.9, then /usr/gcc-sfe/4.8 and /usr/gcc-sfe/4.9
Easy-Setup for build environment
I've started experiments for an easy setup for a build enviroment. I plan to select defaults which can be tuned by a configuration file that is provided in advance, before the package install. This should help automated provisioning in case you plan to make disposable build images (bare metal, KVM, zones or kernel zones).
The main intention is, that the user gets a hands-free installation of the build environment in standard cases. Interactive users may only have to provide very few parameters, for instance in case the compiler like Studio isn't found in predefined/regular default locations.
Update 20160916: Thanks to pjama from down-under there is a tarball with source files for LibreOffice 5 on the way to my workbench. Stay tuned! (and in the meantime, install LibreOffice 4, it _is_ working very well today)
You have questions, feedback, what do you need next?
As always, you know I like questions and feedback very much. You can keep motivation alive easily by providing feedback of any type!
(Artile first published 20160904)