Feedback-ID: i76984098:Fastmail
Message-ID: <b4031552-fa6a-4098-8780-e04da0204561@aklaver.com>
Date: Sun, 20 Oct 2024 10:50:40 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Help Resolving Compiler Errors With enable-dtrace Flag
To: Barry Walker <mstrchef7@gmail.com>, pgsql-general@postgresql.org
References: <CAAiHg9UhjM6XN5XV_NMB184v0UO4H8rHGaBrtwJr0HHok8pJVA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAAiHg9UhjM6XN5XV_NMB184v0UO4H8rHGaBrtwJr0HHok8pJVA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/b4031552-fa6a-4098-8780-e04da0204561%40aklaver.com>
Precedence: bulk

On 10/20/24 09:30, Barry Walker wrote:
> Hey folks,

> 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.

Talking to the folks that created the custom version is not possible?

If you do a diff on:

access/transam/xact.o

between the stock and custom version does it shed any light?

> 
> Thanks!

-- 
Adrian Klaver
adrian.klaver@aklaver.com