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 1pVBoR-000196-E1 for pgsql-novice@arkaria.postgresql.org; Thu, 23 Feb 2023 13:39:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pVBoQ-0004bj-3d for pgsql-novice@arkaria.postgresql.org; Thu, 23 Feb 2023 13:39:06 +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 1pVBoP-0004ba-PN for pgsql-novice@lists.postgresql.org; Thu, 23 Feb 2023 13:39:05 +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 1pVBoM-0006c7-S3 for pgsql-novice@lists.postgresql.org; Thu, 23 Feb 2023 13:39:04 +0000 Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-536be69eadfso186545617b3.1 for ; Thu, 23 Feb 2023 05:39:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=8wA1nXo3r5jqTb3VVfIG7XAnUDyUf0btXLYcxGP8g2M=; b=RNRBGEEulDLogvx1HkyVKq1G9Z7JR7bVoPtPdrLkzb6fIeQI2GsWGOeF3VoLgjvK5O VaLBKbxZX1FqVbIV6QgDn5q4sL6n8ykzIR6jVXHPMag6Q18osBJo1GxgXjI2h2hDtkzf IyIilyTiLp9icAXcy5mNejjjfpCaPCh/ClGslmn9zHyNfFg0GsYqFGHJoVgNsHWzu5cg IRNcyqqIBj/vjCUUQa1D4JLR+/Af8ZUrOgL2jutZp798vGDHKL7RaVrgQomdTRd3y5yK qNETkdAZRjs+BNcFIeLqHx1l12ny23muRndyCxeiJPOwGPPNM4B2Ov6Fr/g598s+Okq9 9tqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=8wA1nXo3r5jqTb3VVfIG7XAnUDyUf0btXLYcxGP8g2M=; b=vhCww1b5oXry7tNS1w/uIEamix0elO3lGoTJuhBNHgNZuG6uAko8Nopa48CGVs/Y5j Fohlg5fTFYy/NIzpoIyMSOqFSibu7I27VBdMNfcL6fLU1ptr8jPc8jPwTRbzjnMl9lBl jwqxhP5r0FDaTFaAaCM3IvMkR03/50JZTKa45NcQCAdJeCHTQcvXg2+gl0cl0ehXQ0Nk xicYShKMGVWWh6ZXCy9qCxziyWcyWwfJn1hyJ71XA4s6a0irev37O3eYDrDtMdznM/oo Q+GINZ+8OQzWgl2NhIAo7rugZxyu5eZyWusnHm4o4qrHvW2n/6heFccM0KUEjbt5tP4f sf8A== X-Gm-Message-State: AO0yUKWllCt8ygkDqJ2OepRqKGVtd+JRAvg2n0UTD3qANU0Hb2qQ6xYl OevOg7fyBUOqHOs6XKG34+mnK2ovP2o7CslK+orI3GvZ2A4= X-Google-Smtp-Source: AK7set+TiMh/8LWv0e8luvPcmrfGr9UaMH/pOkICAwLxgSWqjFWCujb0GUB04AF7At1x4pKYCSx/oSN98A3caL9Kvx4= X-Received: by 2002:a05:6902:34e:b0:9a0:d4d:5d74 with SMTP id e14-20020a056902034e00b009a00d4d5d74mr2068169ybs.3.1677159541632; Thu, 23 Feb 2023 05:39:01 -0800 (PST) MIME-Version: 1.0 From: mahendrakar s Date: Thu, 23 Feb 2023 19:08:50 +0530 Message-ID: Subject: using libjansson in postgres extension To: pgsql-novice Content-Type: multipart/alternative; boundary="000000000000b5f58f05f55e227d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b5f58f05f55e227d Content-Type: text/plain; charset="UTF-8" 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. --000000000000b5f58f05f55e227d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Hackers,

I'm developing an ex= tension where=C2=A0in it indirectly references (libjansson) and libjansson = has a symbol json_object which conflicts with postgres=C2=A0 symbol 'json_object'.

I see below:
PostgreSQL: Documentation: 11: 38.10. C-Language= Functions
"Symbol names defined within object files must not c= onflict with each other or with symbols defined in the PostgreSQL server ex= ecutable. You will have to rename your functions or variables if you get er= ror messages to this effect."

But this re= quires 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 symbo= l.

Thanks,
Mahendrakar.


--000000000000b5f58f05f55e227d--