Right now I have BTC, DOGE & LTC running on it but the QT for EGC I went to hell and back from under the old Distro. Wont run, yes assumptions are like a**holes... everybody has one. I assume it's a library thing.
If you were coping the old binaries over then that's liable to fail as you're unlikely to find the right compatible libraries (windows tends to keep every possible library version around now which is partly why it grows so huge).
Yes that means I have a running wallet. Sooo much easier to do on Mint which I know is one of many flavors that is NOT CentOS and gave me the headaches from before.
If it worked on mint, then it should have worked as easily on Ubuntu or Debian. Without knowing what errors you had on CentOS/Fedora it's hard to suggest what the issue might have been, this also means if there's an issue in the code or instructions then it's not going to get fixed.
Providing some useful error messages etc could have meant you could have got help and you would have helped the community with potential fixes. From me building the daemon on fedora (which tends to be ahead on package versions than debian and its derivatives) we've already found one patch for the code which will benefit debian/ubuntu/mint at some point in the future when they update their package versions.
I didn't transfer anything. I mean I tried but it didn't work. So I successfully built from source and am hoping to be down downloading the chain by days end. What broke it before on Cent was me doing an upgrade or something since it was one of my last deeds before the system went to shit and building on Cent was a nightmare just to get libraries installed.
CentOS 7 x64 IS a nightmare to install and compile ...
This is mainly due to the libraries for OpenSSL, which is due to the crippling of the ECC (secp256k1) that is required for the compile. The other factors are also that the updates to gcc itself, are being followed through with a LOT of the code, so even when trying to compile in other OS (like Debian or Ubuntu) who have the updated gcc libraries and versions, a lot will break in a compile. Some will work though.
This is NOT the fault of the code per se, but more the the creators of the libraries themselves that break the backward compatibility cycle. Admittedly, they usually win in the end, as their gcc code is always moving forward, so the core code of the coin will always need updating, but that usually is only minor adjustments in the grand scheme of things.
CentOS 7 x64 itself is starting to come around, because RedHat are coming around - FINALLY! Damn bureaucratic crap and redtape. If they left OpenSSL ALONE, there would be no major issue with compilations. As it stands, we STILL have to compile in a sandboxed, static environment (made easier by a fully internal rewritten script and VERY powerful servers), where all the components are compiled in a static manner and so the daemon is also. The advantages are great and disadvantages of this method small, but we would SO much like to be able to a full daemon compile in a native dynamic fashion under CentOS 7 x64 and Fedora 27/28 x64 (especially QT versions), both of which are currently almost impossible at the moment.
We will NOT convert our environment from what it is not BTW - just in case that thought crossed your mind
... it stays RHEL based, but we are implementing Debian based systems currently on our new Pyroxene (theMINE) platform, for functionality and availability purposes.
Luckily for us under the script - EGC compiles reasonably well - pity it isn't PoW
#crysx