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 1paXr2-0002if-Ba for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Mar 2023 08:11:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1paXr0-0007kl-NK for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Mar 2023 08:11:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1paXr0-0007kb-CP for pgsql-hackers@lists.postgresql.org; Fri, 10 Mar 2023 08:11:54 +0000 Received: from mail-ua1-x92d.google.com ([2607:f8b0:4864:20::92d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1paXqt-0005Ev-7f for pgsql-hackers@lists.postgresql.org; Fri, 10 Mar 2023 08:11:54 +0000 Received: by mail-ua1-x92d.google.com with SMTP id v48so2949328uad.6 for ; Fri, 10 Mar 2023 00:11:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678435905; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=3OwJ7VJireWnuGI6HyOCZ5mNHfg+5SxR7hV8uUUoh7E=; b=BWb4T6tbI8rjgrBs6G+0MEr0XB/zh0Jlnf6CnHJQsQP2tcKiujKdk/jIBFdLEGLF9N ZLo2vlHX/AqlaZPpyoNHTmjAqtkqgYva3NzwRe8j5IzNCAshbQVtFsMCnTUpWKu4OVBR cBDGeguRWtSncWwJNgRVTMWm+StTZ81jdf35cF9Z8xKSJuME5eqvZyRrkH3e8oVKJJFf ePKAFTD45fcCrLs0WclOGxMK3G0OBJpFHr524pr0XRvLmp44lQkmJ6/s+49KIjRo76Ke z+DcE7dNOkgsZgwt1dddiwVGrokSqqCU7w7GNZpo+zfgBdTPSk5RiU83C3T2tTsU52iI 36hQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678435905; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=3OwJ7VJireWnuGI6HyOCZ5mNHfg+5SxR7hV8uUUoh7E=; b=elreAydWZKIZ2XpD22xPB3ovhOPTxM6j6gNnQsoAWflliWEBikCl1IJJAdECc0dNRN 1I2P/FJ1Z4c2OslIcxHrhKnBgts37bk4Y5iUlYi/eVt8ZgSdqUfV1KyZfyWeXFP+u6CV VEjeGoV6foY5OrHbleihxN2Vtaur8JJkE8y0jeHez5dEBb4wiRfr2R0pLJ7vO6h0JnhA Yro1cpvF/LwAIPj7EljSJssYOek0PcGLgi+lRhqY2dp2gmuiP+uAILbQV04eNeOVe2YN QOJhrDYalsF9dFW2mTp0JdlL8pOkFlM0e+BgmkTXvQM+GqgobJpsT2HIGx17lMZV88VR +iig== X-Gm-Message-State: AO0yUKU3q3hm2pE56f4QCQXYasRXhF1nr0tkPEimW9vz1d+PcM2FHl4i B6e3zV2HRva8gIF8dAY3fIzYF+AOOnkyM6qgb+HjctJqMDw= X-Google-Smtp-Source: AK7set8lgOnlSlGTKu+LPnjpc5LEQJ9w0zP1taJgLAqeJjFnGjXK91nG7JHKYJyMC3vYiuvzkg841MWyDWKlopVZ8h8= X-Received: by 2002:a1f:1888:0:b0:401:8c72:4cf4 with SMTP id 130-20020a1f1888000000b004018c724cf4mr15604413vky.1.1678435905090; Fri, 10 Mar 2023 00:11:45 -0800 (PST) MIME-Version: 1.0 From: Sravan Kumar Date: Fri, 10 Mar 2023 13:41:07 +0530 Message-ID: Subject: Compilation error after redesign of the archive modules To: michael@paquier.xyz, pgsql-hackers@lists.postgresql.org Content-Type: multipart/mixed; boundary="000000000000e6cf7405f6874ffb" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e6cf7405f6874ffb Content-Type: text/plain; charset="UTF-8" Hi, With the redesign of the archive modules: 35739b87dcfef9fc0186aca659f262746fecd778 - Redesign archive modules if we were to compile basic_archive module with USE_PGXS=1, we get compilation error: []$ make USE_PGXS=1 gcc -std=gnu99 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Werror=vla -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -g -g -O0 -fPIC -fvisibility=hidden -I. -I./ -I/home/sravanv/work/workspaces/PGdevel_test/include/postgresql/server -I/home/sravanv/work/workspaces/PGdevel_test/include/postgresql/internal -D_GNU_SOURCE -I/usr/include/libxml2 -c -o basic_archive.o basic_archive.c -MMD -MP -MF .deps/basic_archive.Po basic_archive.c:33:36: fatal error: archive/archive_module.h: No such file or directory #include "archive/archive_module.h" ^ compilation terminated. make: *** [basic_archive.o] Error 1 I have attached a patch that fixes the problem. Can you please review if it makes sense to push this patch? -- Thanks & Regards, Sravan Velagandula EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company --000000000000e6cf7405f6874ffb Content-Type: application/octet-stream; name="v1-0001-fix-archive-module-compilation-error.patch" Content-Disposition: attachment; filename="v1-0001-fix-archive-module-compilation-error.patch" Content-Transfer-Encoding: base64 Content-ID: X-Attachment-Id: f_lf29764t0 RnJvbSA0OWJmZTY3NTBkNmIxNzA5MjI2NzA4ODA4ODMwMjUxZGRkZjkzNDE0IE1vbiBTZXAgMTcg MDA6MDA6MDAgMjAwMQpGcm9tOiBTcmF2YW4gVmVsYWdhbmR1bGEgPHNyYXZhbi52ZWxhZ2FuZHVs YUBlbnRlcnByaXNlZGIuY29tPgpEYXRlOiBUaHUsIDkgTWFyIDIwMjMgMDg6MTg6NDMgLTA1MDAK U3ViamVjdDogW1BBVENIIHYxXSBmaXggYXJjaGl2ZSBtb2R1bGUgY29tcGlsYXRpb24gZXJyb3IK Ci0tLQogc3JjL2luY2x1ZGUvTWFrZWZpbGUgfCAyICstCiAxIGZpbGUgY2hhbmdlZCwgMSBpbnNl cnRpb24oKyksIDEgZGVsZXRpb24oLSkKCmRpZmYgLS1naXQgYS9zcmMvaW5jbHVkZS9NYWtlZmls ZSBiL3NyYy9pbmNsdWRlL01ha2VmaWxlCmluZGV4IDc0NzJjZDVlMDEuLjU2NTc2ZGNmNWMgMTAw NjQ0Ci0tLSBhL3NyYy9pbmNsdWRlL01ha2VmaWxlCisrKyBiL3NyYy9pbmNsdWRlL01ha2VmaWxl CkBAIC0xNyw3ICsxNyw3IEBAIGFsbDogcGdfY29uZmlnLmggcGdfY29uZmlnX2V4dC5oIHBnX2Nv bmZpZ19vcy5oCiAKIAogIyBTdWJkaXJlY3RvcmllcyBjb250YWluaW5nIGluc3RhbGxhYmxlIGhl YWRlcnMKLVNVQkRJUlMgPSBhY2Nlc3MgYm9vdHN0cmFwIGNhdGFsb2cgY29tbWFuZHMgY29tbW9u IGRhdGF0eXBlIFwKK1NVQkRJUlMgPSBhY2Nlc3MgYXJjaGl2ZSBib290c3RyYXAgY2F0YWxvZyBj b21tYW5kcyBjb21tb24gZGF0YXR5cGUgXAogCWV4ZWN1dG9yIGZlX3V0aWxzIGZvcmVpZ24gaml0 IFwKIAlsaWIgbGlicHEgbWIgbm9kZXMgb3B0aW1pemVyIHBhcnNlciBwYXJ0aXRpb25pbmcgcG9z dG1hc3RlciBcCiAJcmVnZXggcmVwbGljYXRpb24gcmV3cml0ZSBcCi0tIAoyLjM4LjEKCg== --000000000000e6cf7405f6874ffb--