Index to SCO OpenServer 5.0.7 issues relating to open source projects
gcc 3.2.x compile fails on SCO Openserver 5.0.7
"we will be adopting GCC 3 as the officially supported version of GCC. This will happen for release 5.0.8 of SCO OpenServer."
"For for GCC 3.x, the first version that will be known to work properly on OSR5 is 3.4."
"If you are feeling brave, when 3.3.1 is released in a few days/weeks, you can get the stuff from the head from CVS, look at the change logs for what I had to do for OSR5 and back-port it. I may do that myself if I have the time, and then get Boyd Lynn-Gerber to post the required patch on his website where he collects such things. In two short weeks we will be releasing a significant update to the GNU Development Tools package, which provides the current officially supported GCC and a plethora of other GNU tools that software developers frequently use. This will rely on Support Level Supplement OSS646B, which is the execution environment update. This update fixes the RTLD, libc and crt*.o files such that they meet the gABI requirements, as outlined above."
gcc 3.4.x C++ compile fails while building libstdc++-v3
"gcc-core builds fine on sco 5.0.7, but the I would like to be able to build a more modern version of the c++ compiler."
"The 3rd stage fails. With the conflict about ::strstr and std::strstr"
"Have you tried a newer GCC? SCO support was removed in GCC 4.3, but 4.2.4 should work, and this problem might already be fixed in that release."
"I took your advice, and attempted to bootstrap gcc 4.2.4 with languages=c,c++ I received a very similar error"
"The problem is an incompatibility between the SCO libc and the GCC you're building, the gcc you use to build is irrelevant."
"In the meanwhile you could try configuring with different options for --enable-cheaders, see https://gcc.gnu.org/onlinedocs/libstdc++/manual/configure.html"
./configure: -v: not found ... error reporting too harsh ...
The full-text of the error is:
The configure script needs a better hint on which compiler to use.
The initial workaround was to specify CC=gcc-3.4.6, but later it was determined that CC=gcc also resolved the problem.