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 1t2ZtX-0059UI-TS for pgsql-general@arkaria.postgresql.org; Sun, 20 Oct 2024 17:39:12 +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 1t2ZtV-00HYBO-Ra for pgsql-general@arkaria.postgresql.org; Sun, 20 Oct 2024 17:39:10 +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 1t2Ypk-00Gzl9-6r for pgsql-general@lists.postgresql.org; Sun, 20 Oct 2024 16:31:12 +0000 Received: from mail-ua1-x92d.google.com ([2607:f8b0:4864:20::92d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t2Ypf-001rlW-HQ for pgsql-general@postgresql.org; Sun, 20 Oct 2024 16:31:11 +0000 Received: by mail-ua1-x92d.google.com with SMTP id a1e0cc1a2514c-84fc818f518so944332241.2 for ; Sun, 20 Oct 2024 09:31:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729441866; x=1730046666; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=w9m5xpioPSGloGScByoKlLhshVV/aw+49lyAgL7xHnI=; b=D7kalnwCSxoZJBz017QllFpI5UJdqe3ENkpLg7xlE7sg4+sT/oPImBfJkkvJt1WkV7 fJAKXcA+mq1tZH/W/F3qOstdh2Ibbvxw9JNrNsJnH6vH3oCWbj8P3HEiFNR5XtEXu7xj 1aDooTOSjgcQQ7gQcTK+Z0oeVULf+gaU8bG5Vbt+tgzavL7YOzxGXUF9oEiJ6xS2kT9F OXW9XAvuVVLWTjKDDemglJiPeAyfq2eUpI3Y4W52inhOukDhYwjA5Q7sNgqWYjQZ96Iu 0Xu+947XnsmoZrzNoK9s3g/dE9mX4ZuR3BX6bKbUwwN4e30CPBRmZP7WfkmkVKxMdYXl yy+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729441866; x=1730046666; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=w9m5xpioPSGloGScByoKlLhshVV/aw+49lyAgL7xHnI=; b=c9VqmizE34qgkd2kwst68SIqsi0krGvlx5VX+K/b7DCLEFl4OFh4KVGQfXXeuS6DAY lTVp7qYFsX0Rrary4auQ0VNe1gZIAAOUJcUnvPXM/6xF8nTktXF9TCCTvS3/ASMpOuin +UBzxUnEboNSW4eV+X/UzWgbwdS4+a2DqyBRmkla0vfw4RElYiw7RimLwf1DjX9t+4MA Q1o2UrapRcCGg2RiUkJ/nkgiut0EYdsKJHK3K8I6tBvp6TIyl5dtTJQc+0JUtF+hQRFI yZFddTqgyn6tQPAD/YlCjIM9lVxkFgJn25C/EQWvy01dICKxI40AEZGUCExz1gfXKLFZ QQGA== X-Gm-Message-State: AOJu0YyJRLOUHDZac9RV+zCm2kHKtPg9OdnM8jzhHiPuQIDo3b1Kk9Kr BSWwqjFxp065G3mpB9qldOIZ4WxKOCNLMcrHUwcMgoNyaoGHIuou5vOJqQGkSVDIGpb80uTNo0O fXEiekRazVklNKMPzeqe1UHLcULzK0whz X-Google-Smtp-Source: AGHT+IE+4+FGuaiQ2mFXfk0yRFPdAAZHYe9ka4U3ZwIvjSU+poAbxVZ9ZulGydUlEx3KAaWvEN2AcABtnzgnofNSsYw= X-Received: by 2002:a05:6102:c51:b0:493:c3b2:b5ba with SMTP id ada2fe7eead31-4a5d6a91e7emr6757451137.6.1729441866239; Sun, 20 Oct 2024 09:31:06 -0700 (PDT) MIME-Version: 1.0 From: Barry Walker Date: Sun, 20 Oct 2024 12:30:55 -0400 Message-ID: Subject: Help Resolving Compiler Errors With enable-dtrace Flag To: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="00000000000018d5ae0624eb10df" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000018d5ae0624eb10df Content-Type: text/plain; charset="UTF-8" Hey folks, I'm working on a custom version of Postgres that is roughly in line with 16.4 but has customizations in it. I'm trying to compile this custom version (on Linux) with `--enable-dtrace` but I'm running into an issue during the linker stage. I've done a clean and full rebuild but that doesn't help fix the problem. I get these errors for all probes: access/transam/xact.o(.note.stapsdt+0x24): error: undefined reference to 'postgresql_transaction__start_semaphore' access/transam/xact.o(.note.stapsdt+0x78): error: undefined reference to 'postgresql_transaction__commit_semaphore' access/transam/xact.o(.note.stapsdt+0xcc): error: undefined reference to 'postgresql_transaction__abort_semaphore' I can see the probes.h file gets generated what looks to be correctly, specifically these: __extension__ extern unsigned short postgresql_transaction__commit_semaphore __attribute__ ((unused)) __attribute__ ((section (".probes"))); I have compiled vanilla pg16.4 with the same flags and the probes got created and linked as expected with no issues so I'm assuming there is some difference in the custom version that is causing the errors but I'm having a hard time tracking it down. I'm wondering if anyone here has any experience with this error or has any hints as to why the linker can't find these definitions or even just where the actual definitions for these probes should live so I can try to work backwards and see if there is any differences in the custom version that is messing with the linker. Thanks! --00000000000018d5ae0624eb10df Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey folks,

I'm wor= king on a custom version of Postgres that is roughly in line with 16.4 but = has customizations in it. I'm trying to compile this custom version (on= Linux) with `--enable-dtrace` but I'm running into an issue during the= linker stage. I've done a clean and full rebuild but that doesn't = help fix the problem. I get these errors for all probes:

access/transam/xact.o(.note.stapsdt+0x24): error: undefined reference to '=
postgresql_transaction__start_semaphore'
access/transam/xact.o(.note.stapsdt+to 'postgre=
sql_transaction__commit_semaphore'
access/transam/xact.o(.note.stapsdt+to 'postgre=
sql_transaction__abort_semaphore'
I can see the probes=
.h file gets generated what looks to be correctly, specifically these:
__extension__ extern unsigned short postgresql_tran=
saction__commit_semaphore __attribute__ ((unused)) __attribute__ ((section =
(".probes")));
I have compiled vanil= la pg16.4 with the same flags and the probes got created and linked as expe= cted with no issues so I'm assuming there is some difference in the cus= tom version that is causing=C2=A0the errors but I'm having a hard time = tracking it down. I'm wondering if anyone here has any experience=C2=A0= with this error or has any hints as to why the linker can't find these = definitions or even just where the actual definitions for these probes shou= ld live so I can try to work backwards and see if there is any differences = in the custom version that is messing with the=C2=A0linker.

<= /div>
Thanks!
--00000000000018d5ae0624eb10df--