On 30-10-15 10:41, Martin wrote: > On Thu, Oct 29, 2015 at 2:37 AM, Riccardo Murri <[email protected] > <mailto:[email protected]>> wrote: > > > Why, oh why, would you need a GCC that old on a recent system? > > To compile code that was known to compile correctly with GCC 4.5 and is > no longer accepted by GCC 4.9. (Later on, I found about `-fpermissive` > but I still think that `.eb` files should either work or be removed from > the repo if they cannot be built any more ;-)) > > > I thought the promise that we can rebuild things is one of the core > promises of easybuild? > > I have to admit I'm a bit worried. I *heavily* rely on this to be > covered by the "reproducible build" argument that comes up every other > thread. > > So what if I decide to switch distros or create another cluster that > replaces the current one, shouldn't I be able to rebuild the stuff > without needing to worry about the underlying distribution?
Well, building GCC (especially older GCC on newer systems) has always been difficult. If you would switch distro to something untested (like Slackware), you probably bump into a few issues. Nothing we cannot solve but sometimes, distro just do weird stuff. Like move a file to a subdirectory in this case. Or lib/lib64 weirdness on opensuse. Ward
