Re: FreeTDS port to VMS V9.x on x86?

On 6/6/2025 11:14 AM, Craig A. Berry wrote:

On 6/6/25 9:42 AM, Arne Vajhøj wrote:

And now dbfcmd works.
>
Of course it does not explain why the replacement doesn't work.

 Nor why the detection code doesn't correctly identify that vasprintf is
present.  That detection code has been there unchanged for 23 years:
 https://github.com/FreeTDS/freetds/blob/ a381342bbfccafc0aa9ed2376e38470907d53225/vms/configure.com#L267
 #include <stdarg.h>
#include <stdio.h>
#include <stdlib.h>
int main()
{
char *ptr;
vasprintf(&ptr,"%d,%d",1,2);
exit(0);
}
 But it isn't using va_start/va_end, which it surely should. My guess is
this worked by accident on pre-x86 but something tightened up on x86
that makes the vasprintf call fail and causes FreeTDS to use its
fallback implementation.  I'm without access at the moment so can't test
this theory out myself.

I can confirm that.
On x86-64:
$ typ zzz.c
#include <stdarg.h>
#include <stdio.h>
#include <stdlib.h>
int main()
{
char *ptr;
vasprintf(&ptr,"%d,%d",1,2);
exit(0);
}
$ cc zzz
vasprintf(&ptr,"%d,%d",1,2);
.......................^
%CC-W-CVTDIFTYPES, In this statement, "1" of type "int", is being converted to "long pointer to char".
at line number 7 in file DKA0:[arne.freetds]zzz.c;1
vasprintf(&ptr,"%d,%d",1,2);
^
%CC-E-TOOMANYARGS, In this statement, "vasprintf" expects 3 arguments, but 4 are supplied.
at line number 7 in file DKA0:[arne.freetds]zzz.c;1
Arne