python-backports_abc-0.5-1.aix6.1.noarch.rpm issue

[Michael]

Thx for the update.

Curious - why use gcc for compiler (as that is not 'native' compiler for AIX)? More specifically, why not use xlc - which the runt-time environment AIX provides and updates continually.

[Teej]

The vast majority of packages that we are depending on for Python are highly dependent on GCC for compilation and installation.  I just completed an installation of 180+ Python modules, with most of it source code being compiled on AIX.

Before we switched to GCC, we had a constant issue of updating the make file to be compatible with AIX's make; updating C files to be compatible with xlC, and so on forth.  With the switch to GCC, we only encountered 3 individual issues, all with tickets opened to the respective developers to improve compatibility.

We just simply do not have the time to figure everything out on AIX using xlC.

[Michael]

Thx for the update. Sad to read about it though.

I have run into similar issues - where OSS developers considered themselves portable, by definition, because they use gcc. I suppose it is a way to define portable, but not the way I was "taught" over 30 years ago.

From experience I know relying on gcc on AIX creates new issues, but smaller than you are facing atm. And issues that will never go away because noone bothers to confront people about the non-existent port-ability of certain blocks of code (usually there are ifdef's et al in the code for windows, but not for "UNIX"/"POSIX").

Glad you have been/are successful with your goals!