Re: Problem linking with Release library
Igor Korot <ikorot01@gmail.com>
From: Igor Korot <ikorot01@gmail.com>
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2026-05-13T04:59:41Z
Lists: pgsql-general
Hi, Ron, On Tue, May 12, 2026 at 8:10 PM Ron Johnson <ronljohnsonjr@gmail.com> wrote: > On Tue, May 12, 2026 at 10:52 PM Igor Korot <ikorot01@gmail.com> wrote: > [snip] > >> I’m not running Postgres server. It is running on the different machines. >> All I need is to build the client library. Why can’t I? Why it should >> matter what software (OS/compiler) I’m using? As long as I can successfully >> build my software and test it it should be fine. >> > > David made it pretty clear: the *PGDG changed the toolchain*, > It didn’t change the toolchain - it changed configuration tools. But it’s not the point. The point I’m making is that the software was providing the makefile and now it does not. Thank you. and decided *not to support* an OS that went *EOL* three years ago, and a > compiler that's only getting security updates: "There is no guarantee or > real attempt to keep modern supported versions running on software > obsoleted before they even came into existence." > > -- > Death to <Redacted>, and butter sauce. > Don't boil me, I'm still alive. > <Redacted> lobster! >
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Remove MSVC scripts
- 1301c80b2167 17.0 cited