On Fri, Mar 20, 2015 at 04:51:55AM +0300, Max Filippov wrote: > xtensa-linux-gcc -o conftest -Wall -Wmissing-prototypes > -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels > -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing > -fwrapv -fexcess-precision=standard -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -mlongcalls > -mtext-section-literals -Os -pthread -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE conftest.c > -lssl -lcrypto -lz -lreadline -lrt -lcrypt -ldl -lm > > and if I drop irrelevant libraries from that command its stdout+stderr > will probably be empty. > > But I was curious why this test is written *that* way.
Threading compiles are different for every platform so the code just tries everything --- we didn't anticipate that adding a useless library would actually cause a failure. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
