Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pVNN5-0008UB-8c for pgsql-novice@arkaria.postgresql.org; Fri, 24 Feb 2023 01:59:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pVNN4-0002kN-51 for pgsql-novice@arkaria.postgresql.org; Fri, 24 Feb 2023 01:59:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pVNN3-0002kE-Mj for pgsql-novice@lists.postgresql.org; Fri, 24 Feb 2023 01:59:37 +0000 Received: from mail-yw1-x112f.google.com ([2607:f8b0:4864:20::112f]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pVNN1-0004h8-6m for pgsql-novice@lists.postgresql.org; Fri, 24 Feb 2023 01:59:36 +0000 Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-53852143afcso99609297b3.3 for ; Thu, 23 Feb 2023 17:59:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=Lk0Osse1zT4QtX+DEWFjbJocpx7q7c0Ci9OxRU8WoEU=; b=mvrHX+NiNgoXx61xPsZn32l3ZujiOljKSrIgf2IA1PmhdBP/LSdwA/JoktHs6W9KTm C2VgU9yzUwqA+4cgbdJzccZJ7edvRp2iklNceO4mNXFsJMzgJQ4T7n19uIv8cX7eA9K0 Vfdw4rDCfCmpx0R+PMtgK4EYGf9/+Eay2PQvlqpuclvGDttSQ/qiflbcKMkM+8jJ3+Un a5UsaG3mPTzNcdcSJxo/remD5X1VgYnzab6jdfd61sXp0CmPjTk71f4qEkvlgu751/2K gHfx8gmhwoGClmrtFR5mq4IfN8W+H6G1/czCsNuRLQwWyiLIPi4F1HAwEV9jCxRVuCqz +Yww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=Lk0Osse1zT4QtX+DEWFjbJocpx7q7c0Ci9OxRU8WoEU=; b=f1T+Be24eGd8GBDIWFxNdqtQJMex/GG5DD4zz+lDJvxVh7rH8QMc3k2iGIGVOQdaRJ R8c8L3+BYYPRKukoBCi0XVeklDqJnt2HJR+4PIUxoCBgt5IcMmsiKwyKc4t/AWwBll1h 6QiQOjsqcb4BdoPUCmprVvrFlamxkXjgYryM0Gflc8EBdH/60tXfJGX90+Vaisqs+KaE FOARVAC9BUxVZHDUh8/YPqG9uBsPBtgMms+mDBIjBsVXrxeg0t6hMPk+W8KVS5n9tr5N CLedo4B0QZ7n64xMmKIxghhJXCIjEu7DPRTa8naslQSDqKRv17s62xdapCoKAHlNVC8a zStQ== X-Gm-Message-State: AO0yUKWoJvJ7tSkreuAtytPXQYfnSZIcEnxYG7KEvFesCUGea541rFgP ZqF1zpn8fdrjfCWHUCLzree6isNR470xPTQhTWqIKmvZ X-Google-Smtp-Source: AK7set/CNI1sxBudnk5RVAVyvIoaqarTskPD+purE4D994+RZjLeD/1whk0LMVWWhIkofiTWRrIIC39Kyv9zvFJBF78= X-Received: by 2002:a25:8d8f:0:b0:a37:6849:d454 with SMTP id o15-20020a258d8f000000b00a376849d454mr1416328ybl.3.1677203974345; Thu, 23 Feb 2023 17:59:34 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: mahendrakar s Date: Fri, 24 Feb 2023 07:29:23 +0530 Message-ID: Subject: Re: using libjansson in postgres extension To: pgsql-novice , andrew@dunslane.net Content-Type: multipart/alternative; boundary="0000000000001b56f205f5687bd5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001b56f205f5687bd5 Content-Type: text/plain; charset="UTF-8" +andrew. Thoughts? On Thu, 23 Feb 2023 at 19:08, mahendrakar s wrote: > Hello Hackers, > > I'm developing an extension where in it indirectly references (libjansson) > and libjansson has a symbol json_object > which > conflicts with postgres symbol 'json_object > > '. > > I see below: > PostgreSQL: Documentation: 11: 38.10. C-Language Functions > > "Symbol names defined within object files must not conflict with each > other or with symbols defined in the PostgreSQL server executable. You will > have to rename your functions or variables if you get error messages to > this effect." > > But this requires to maintain libjansson with customizations(have a > different symbol) to meet the needs. > > Do you have any suggestions to use the libjansson 'as it is' without using > the different symbol. > > Thanks, > Mahendrakar. > > > --0000000000001b56f205f5687bd5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thoughts?

On = Thu, 23 Feb 2023 at 19:08, mahendrakar s <mahendrakarforpg@gmail.com> wrote:
Hello Hackers,
I'm developing an extension where=C2=A0in it indirect= ly references (libjansson) and libjansson has a symbol json_object which conflict= s with postgres=C2=A0 symbol 'json_object'.

<= div>I see below:
PostgreSQL: Documentation: = 11: 38.10. C-Language Functions
"Symbol names defined within ob= ject files must not conflict with each other or with symbols defined in the= PostgreSQL server executable. You will have to rename your functions or va= riables if you get error messages to this effect."

<= /div>
But this requires to maintain libjansson with customizations(have= a different symbol) to meet the needs.

Do you= have any suggestions to use the libjansson 'as it is' without usin= g the different symbol.

Thanks,
Mahendra= kar.


--0000000000001b56f205f5687bd5--