| From: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Problem linking with Release library |
| Date: | 2026-05-14 08:38:55 |
| Message-ID: | 2yihtpsvyp5kuiq2j62oyamseoeffqjfmje44m62c2mfh7u2sd@ywgtxy5ghynm |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2026-05-12 21:59:41 -0700, Igor Korot wrote:
> On Tue, May 12, 2026 at 8:10 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
>
> On Tue, May 12, 2026 at 10:52 PM Igor Korot <ikorot01(at)gmail(dot)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.
They switched from Make to Meson. In my book the build automation tool
is very much part of the toolchain.
> The point I’m making is that the software was providing the makefile and now it
> does not.
Because they now use Meson instead of Make. Meson doesn't use Makefiles
but dependency files with a different syntax.
hjp
--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp(at)hjp(dot)at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2026-05-14 08:46:47 | Re: Problem linking with Release library |
| Previous Message | Igor Korot | 2026-05-13 06:23:21 | Re: Problem linking with Release library |