"Paragon Corporation" writes:
>> Huh. Apparently, whichever Windows compiler you're using defines
>> PRId64 as "d", which surely seems pretty broken.
> I think it was only failing on the postgresql function calls.
> And this: gcc -Wall -E testint.c | grep '\(printf.*x)\| int64_t;\)'
> Returne
Alvaro and Tom,
A big thank you. That seems to have done the trick. My compiler warnings
went away and no more syntax errors in the regress tests. I still have some
regress failures I got to hunt down, but those could be caused by places in
the code I did not replace PRId64 calls or something e
"Paragon Corporation" writes:
> I've been currently suffering an issue in mingw64 with changes made in
> PostGIS topology code base. Sadly it only happens to me (compiling in
> mingw64)
> Issue is when code like this was introduced
> appendStringInfo(str, "%s%" PRId64, sep, edge->start_node);
Paragon Corporation wrote:
> I've been currently suffering an issue in mingw64 with changes made in
> PostGIS topology code base. Sadly it only happens to me (compiling in
> mingw64)
>
> Issue is when code like this was introduced
>
>
> appendStringInfo(str, "%s%" PRId64, sep, edge->start_nod
I've been currently suffering an issue in mingw64 with changes made in
PostGIS topology code base. Sadly it only happens to me (compiling in
mingw64)
Issue is when code like this was introduced
appendStringInfo(str, "%s%" PRId64, sep, edge->start_node);
Which uses a PostgreSQL function appe
