Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qdQQD-003L6T-58 for pgsql-odbc@arkaria.postgresql.org; Tue, 05 Sep 2023 07:24:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qdQQB-0000Uc-SU for pgsql-odbc@arkaria.postgresql.org; Tue, 05 Sep 2023 07:24:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qdCRX-00D383-7A for pgsql-odbc@lists.postgresql.org; Mon, 04 Sep 2023 16:28:51 +0000 Received: from mail-yb1-xb2e.google.com ([2607:f8b0:4864:20::b2e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qdCRT-002iGw-7u for pgsql-odbc@postgresql.org; Mon, 04 Sep 2023 16:28:49 +0000 Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-d7b8d2631fdso1421578276.3 for ; Mon, 04 Sep 2023 09:28:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1693844926; x=1694449726; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=b7ymAzXDuAqx1OcXbaWTU1oAYEKWZlozqgv121QnmWo=; b=K8Bu0d0a3AIKCr1CanYpzEg9zvHcQWblXk8wJ7Aw4/32pC2QQc1WLNpBCaP1XUP1qP 2hdLzQobZyqJZXzYJ1dXqDKZZG1hPzdhBDTwH4wmS4/6Wvm4xk566YvCynaGi5CQrtqz +YVaJzBZ9ZPzJyT2vYPEzL73rwryQgxhFFw9q1dBa+pN2HQCCNy48Vi0ia4zC6Ah1tfF tASBMMA1KvA2ZEtoZbNpdnL1WfS+Vydrc3//RZ7hADi27XzX68sfY6EDfqiw4CMcO1eL q724pnDwIOfFaL9WLbKEjZ3I91UoEhWhqfaly6VFFYDXCVAPolCamJai37zxb3KfhNPT BJPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693844926; x=1694449726; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=b7ymAzXDuAqx1OcXbaWTU1oAYEKWZlozqgv121QnmWo=; b=c785R3cDbsdE6TpUxt20jktHGs0Qnt4/Z8MysUIJXEPOvBMLt4LmVpXpiWagCBvCFh JNtKuS4a1km/3aEpsVPcS5eaxFfeO79jbuYZ8SMl/fnSLaXNmH0AuAm/RqAc0cTgbzI2 OWYX/OIGlumgxduvCLih7cZgf8yfkoh5U/kc2jjHPkJGuqcqOr2dvC4zZ2mK4L5HQH+D BGbLYIlp6n5SvcsPTFpHtBW1LbOUB/WbmDTGOCE4Vf/bav2D+WRKbEcftnKMI4TlJ0ls oQHmbAYdwE09RWxmGA/6zcaDLXVtYeF3BMBUMQQ2bNyCJuePu8w4UB5iB6VUxU3UtLU+ FiJg== X-Gm-Message-State: AOJu0YyDfsbroP7adtyTPfaFc6b13UJALmmChJB8BxkKLa4JXeNHqvWr BEtaLLM1islfsfJsuVMGPsZRvVTNRfS1ylHf8syPTQ== X-Google-Smtp-Source: AGHT+IFz5eNd6S//pXQmE4lBqqQsyEj237u7Fj0VbNAt6i/YAERmJgiRdQz+EVs5C0CHtQLm10Bro+Sxyk/i8x+GOSo= X-Received: by 2002:a25:d481:0:b0:d1a:65c9:d98f with SMTP id m123-20020a25d481000000b00d1a65c9d98fmr12316380ybf.56.1693844926301; Mon, 04 Sep 2023 09:28:46 -0700 (PDT) MIME-Version: 1.0 References: <5D27E7EF-BBA7-4A44-8FA5-17BAEFED6EB4@enterprisedb.com> In-Reply-To: From: Moazzum Ali Date: Mon, 4 Sep 2023 21:27:49 +0500 Message-ID: Subject: Re: Psqlodbc build fails on linux To: Dave Cramer Cc: Michael Paquier , pgsql-odbc@postgresql.org Content-Type: multipart/alternative; boundary="00000000000023314006048b014b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000023314006048b014b Content-Type: text/plain; charset="UTF-8" Dave, Is it something that can be fixed on PG or psqlodbc side or you would also suggest what Michael suggested? I have tried that environment rule though and it works. Thanks, Moazzum On Mon, Sep 4, 2023, 9:07 PM Dave Cramer wrote: > > > On Mon, 4 Sept 2023 at 10:23, Dave Cramer > wrote: > >> >> >> On Sun, 3 Sept 2023 at 19:46, Michael Paquier >> wrote: >> >>> On Thu, Aug 31, 2023 at 06:28:06AM +0500, Moazzum Ali wrote: >>> > One way to fix the error is to include the following line before >>> > #include "pqexpbuffer.h" in connection.h and statement.h >>> > #include >>> >>> Wouldn't it be better to enforce an environment rule in psqlodbc.h >>> instead? PostgreSQL enforces PG_USE_STDBOOL already on Windows, and >>> I am pretty sure that it would be OK to do the same in other *nix >>> places where anybody cares about ODBC. >>> >> >> I'm guessing this is a debian thing as I just built this successfully on >> a redhat (ish) system >> > > It pays to read all of the above before trying to replicate. I was > building against 15, not 16 > I see the failure now > >> >> Dave >> > --00000000000023314006048b014b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dave,

Is it someth= ing that can be fixed on PG or psqlodbc side or you would also suggest what= Michael suggested? I have tried that environment rule though and it works.=

Thanks,
Moazzum

On Mon, Sep 4, 2023, 9:07 PM Dave Cramer <= davecramer@postgres.rocks> wrote:


On Mon, 4 Sept 2023 at 10:23, Dave = Cramer <davecramer@postgres.rocks> wrote:


On S= un, 3 Sept 2023 at 19:46, Michael Paquier <michael@paquier.xyz> = wrote:
On Thu, A= ug 31, 2023 at 06:28:06AM +0500, Moazzum Ali wrote:
> One way to fix the error is to include the following line before
> #include "pqexpbuffer.h" in connection.h and statement.h
> #include <stdbool.h>

Wouldn't it be better to enforce an environment rule in psqlodbc.h
instead?=C2=A0 PostgreSQL enforces PG_USE_STDBOOL already on Windows, and I am pretty sure that it would be OK to do the same in other *nix
places where anybody cares about ODBC.

= I'm guessing this is a debian thing as I just built this successfully o= n a redhat (ish) system=C2=A0

=
It pays to read all of the above before trying to replicate. I was bui= lding against 15, not 16
I see the failure now=C2=A0

Dave
--00000000000023314006048b014b--