Hi David,
I understand your frustration.
I did not look in detail to this problem, but as far as we are concerned, we plan to port our product on AIX 7.3, potentially with IBM V17 compiler, so I need a solution.
If this issue is filed somewhere at IBM or HCL issue database, I would appreciate to get a ticket number/id, and we'll watch for a fix / new CSDK release.
Otherwise, short term, if patching the esql script is the solution, we'll do that.
Seb
------------------------------
Sebastien FLAESCH
------------------------------
Original Message:
Sent: Wed June 18, 2025 12:00 PM
From: David Williams
Subject: informix 15 esql in conjunction with latest AIX compiler generation
Hi,
Go back to the AIX compiler people at tell them to not break people's compile scripts!
If they want to change the name of the compiler binary and flags then they should make that a new product and not break compatability in v17.
I would move to gcc, it is free and I have not had compatability issues with it!
Regards,
David.
------------------------------
David Williams
Senior Database Platform Engineer
Flutter
London
Original Message:
Sent: Tue April 08, 2025 03:36 AM
From: Peter Weigert
Subject: informix 15 esql in conjunction with latest AIX compiler generation
Dear community!
In the Machine Notes for my Installation is noted that:
1. This product was built on AIX 7.2 Technology using the following
compilers:
IBM XL C/C++ for AIX, V16.1.0 (5725-C72, 5765-J12)
XL C/C++ Runtime 16.1.0.10
That is quite ok for me, but when it comes to the point to use the esql command I am failing on the specific issue that we need to proceed to the V17 compiler generation which is installed on the machine. esql assumes, the compiler to be named xlclang by default. This can be overridden by defining $INFORMIXC in the environment. But still I need to modify the installed esql-script, as they imply fixed compiler flags:
CC="${INFORMIXC=xlclang} -qchars=signed -m64 -qcheck=nullptr -qmaxmem=-1 -qspill=2000"
In the V17 compiler generation the compiler is named by one of these entry-names:
-rwxr-xr-x 1 root system 442 Oct 18 2023 ibm-clang
-rwxr-xr-x 1 root system 488 Oct 18 2023 ibm-clang++_r
-rwxr-xr-x 1 root system 460 Oct 18 2023 ibm-clang-cpp
-rwxr-xr-x 1 root system 468 Oct 18 2023 ibm-clang_r
But none of these is supporting the legacy options named by -q. We may modify this to "-fsigned-char -m64 -fsanitize=nullability" (hopefully it's really the same) but for the spillsize i did not find a viable equivalent.
On the other hand the 13.1.3 compiler can't manage the -m64 option which requires to be modifed to -q64
I do not want to change the esql command, but I see no other options for now. Does anyone have a suggestion?
krgds Peter
------------------------------
Peter Weigert
------------------------------