Andres Freund <and...@anarazel.de> writes:
> The strerror push, I assume it's that at least, broke something on icc:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fulmar&dt=2018-09-26%2018%3A00%3A16
Yeah. It looks like the problem is that configure's test for strerror_r's
return type does not work on icc:
onfigure:10784: checking whether strerror_r returns int
configure:10805: icc -std=gnu99 -c -mp1 -fno-strict-aliasing -g -O2 -pthread
-D_REENTRANT -D_THREAD_SAFE -D_POSIX_PTHREAD_SEMANTICS -D_GNU_SOURCE
-I/usr/include/libxml2 conftest.c >&5
conftest.c(45): warning #159: declaration is incompatible with previous
"strerror_r" (declared at line 438 of "/usr/include/string.h")
int strerror_r(int, char *, size_t);
^
configure:10805: $? = 0
configure:10812: result: yes
Configure is expecting this to throw a hard error (if the platform
declares strerror_r to return char*) but icc only makes it a warning.
What I am not quite figuring out here is how the code seemed to work
before. Before this patch, it only mattered in libpq because that was the
only place using pqStrerror. Maybe the regression tests don't ever
produce a strerror output from libpq?
regards, tom lane
